Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d44efee983e50e547f6ebc35752e98744733e3fa583ccb0a601683c743c25675

Tx prefix hash: c41f8dcf1efa3869e1f2838255f219c17e1e195e03bea883564bd46245f4f4e9
Tx public key: 6e022a434a709a0c5578dbd0b857886e1cb3fb1e91c5217e94370a46c46e3d6e
Timestamp: 1711426282 Timestamp [UCT]: 2024-03-26 04:11:22 Age [y:d:h:m:s]: 00:294:22:38:48
Block: 986498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211102 RingCT/type: yes/0
Extra: 016e022a434a709a0c5578dbd0b857886e1cb3fb1e91c5217e94370a46c46e3d6e02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eaec44bb8a1b0d017be0fa9741d7e34faba3d10dd09be2c9f8ef41bbd1d90d8 0.600000000000 1446727 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": 986508, "vin": [ { "gen": { "height": 986498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eaec44bb8a1b0d017be0fa9741d7e34faba3d10dd09be2c9f8ef41bbd1d90d8" } } ], "extra": [ 1, 110, 2, 42, 67, 74, 112, 154, 12, 85, 120, 219, 208, 184, 87, 136, 110, 28, 179, 251, 30, 145, 197, 33, 126, 148, 55, 10, 70, 196, 110, 61, 110, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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