Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: deff0101b2890fe56b543e23348c1308e6267ae1edce505f4950ff53c191c48f

Tx prefix hash: 92957c852ac8445e2f5db5ea4f0f777b9f8894e966ca27c47002ffcb77f2de50
Tx public key: 1fd6917c02d3012e24c1c602cc3ebaa1da0e35cc26ff3ef10f699783d0fdd8fd
Timestamp: 1710579346 Timestamp [UCT]: 2024-03-16 08:55:46 Age [y:d:h:m:s]: 01:012:23:28:40
Block: 979471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270240 RingCT/type: yes/0
Extra: 011fd6917c02d3012e24c1c602cc3ebaa1da0e35cc26ff3ef10f699783d0fdd8fd02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0974c3af7d156bc0aacd11a2add1e6767f4a59d1dc253b09aa2c8c1a46ea413 0.600000000000 1439504 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": 979481, "vin": [ { "gen": { "height": 979471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0974c3af7d156bc0aacd11a2add1e6767f4a59d1dc253b09aa2c8c1a46ea413" } } ], "extra": [ 1, 31, 214, 145, 124, 2, 211, 1, 46, 36, 193, 198, 2, 204, 62, 186, 161, 218, 14, 53, 204, 38, 255, 62, 241, 15, 105, 151, 131, 208, 253, 216, 253, 2, 17, 0, 0, 0, 5, 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