Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f180e2aef44aeec6ffa0cc3c99deb9e70ce6680c36d52c736a7beeccb9c8a71

Tx prefix hash: d61b765d06fd85573a28fcddcea1419c6a0ae4490df2c8d1043ff4a6602709a8
Tx public key: e5b85dbc3982397e7d5bddf53d311bcff199dc635a6f1db551171be7b73356d2
Timestamp: 1704742602 Timestamp [UCT]: 2024-01-08 19:36:42 Age [y:d:h:m:s]: 01:080:04:13:36
Block: 931052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318401 RingCT/type: yes/0
Extra: 01e5b85dbc3982397e7d5bddf53d311bcff199dc635a6f1db551171be7b73356d20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c6568b4bb221042406aa1cc8a077e755c4cd5c96205a028396d5a31e0403ba7 0.600000000000 1388944 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": 931062, "vin": [ { "gen": { "height": 931052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c6568b4bb221042406aa1cc8a077e755c4cd5c96205a028396d5a31e0403ba7" } } ], "extra": [ 1, 229, 184, 93, 188, 57, 130, 57, 126, 125, 91, 221, 245, 61, 49, 27, 207, 241, 153, 220, 99, 90, 111, 29, 181, 81, 23, 27, 231, 183, 51, 86, 210, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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