Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0d1a3a068c15c61c0f0295b0fe4af17b79db9eb1cadd3de662f350dc079d39ff

Tx prefix hash: ccd44b6eacc1db4cb836358f00779b828103d70eeee59317ab885793162027fc
Tx public key: f1a0b7d1f4b67d48e330918f6078c0dce160dfd1320eec8842e4f68c523661c6
Timestamp: 1588734013 Timestamp [UCT]: 2020-05-06 03:00:13 Age [y:d:h:m:s]: 04:208:19:13:45
Block: 98690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1065867 RingCT/type: yes/0
Extra: 01f1a0b7d1f4b67d48e330918f6078c0dce160dfd1320eec8842e4f68c523661c602110000000486362411000000000000000000

1 output(s) for total of 289.067872194000 dcy

stealth address amount amount idx
00: 158cf19cb3df7ef9fb75abc933c24cb7ee23ea440f2af1b3326f64f6a765b67f 289.067872194000 174416 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 98700, "vin": [ { "gen": { "height": 98690 } } ], "vout": [ { "amount": 289067872194, "target": { "key": "158cf19cb3df7ef9fb75abc933c24cb7ee23ea440f2af1b3326f64f6a765b67f" } } ], "extra": [ 1, 241, 160, 183, 209, 244, 182, 125, 72, 227, 48, 145, 143, 96, 120, 192, 220, 225, 96, 223, 209, 50, 14, 236, 136, 66, 228, 246, 140, 82, 54, 97, 198, 2, 17, 0, 0, 0, 4, 134, 54, 36, 17, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8