Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30a03d102c03ffdae7eae97dba6c3c60482f96f552c5a54ea97985b248a712d5

Tx prefix hash: 11f7f54881cc22700f79d33ae1a22d2e27310c5ef17ba27298a3abfced059961
Tx public key: dbf10ab1a6df48e3b2dffe98e4f8a9e660a089b1ffa626cdfc6542f255a8adb7
Timestamp: 1705188799 Timestamp [UCT]: 2024-01-13 23:33:19 Age [y:d:h:m:s]: 01:149:04:57:31
Block: 934751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367768 RingCT/type: yes/0
Extra: 01dbf10ab1a6df48e3b2dffe98e4f8a9e660a089b1ffa626cdfc6542f255a8adb70211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a33047fc0f4530cf85f67434c728a2b189fd053a2b5491faaff8965bea75a916 0.600000000000 1392767 of 15

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": 934761, "vin": [ { "gen": { "height": 934751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a33047fc0f4530cf85f67434c728a2b189fd053a2b5491faaff8965bea75a916" } } ], "extra": [ 1, 219, 241, 10, 177, 166, 223, 72, 227, 178, 223, 254, 152, 228, 248, 169, 230, 96, 160, 137, 177, 255, 166, 38, 205, 252, 101, 66, 242, 85, 168, 173, 183, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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