Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c33e0645d02c8868cb5602ad1e2d9e70e26dae920eb80bcc499607305d93737

Tx prefix hash: 313449b9695b9d3e56eaf0238a17c45e42ea55f065193ff9268fb399a17c58e8
Tx public key: 6f7661d29c5a09782b029b02dbbe4ad9248500af17174f0b4c4d7641a57e268f
Timestamp: 1723595229 Timestamp [UCT]: 2024-08-14 00:27:09 Age [y:d:h:m:s]: 00:283:11:20:21
Block: 1087362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202518 RingCT/type: yes/0
Extra: 016f7661d29c5a09782b029b02dbbe4ad9248500af17174f0b4c4d7641a57e268f02110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de9fc3e47d3374423d4ae5dbaab13ccb0cbd935ced445fe6e948e0ade702a85e 0.600000000000 1561971 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": 1087372, "vin": [ { "gen": { "height": 1087362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de9fc3e47d3374423d4ae5dbaab13ccb0cbd935ced445fe6e948e0ade702a85e" } } ], "extra": [ 1, 111, 118, 97, 210, 156, 90, 9, 120, 43, 2, 155, 2, 219, 190, 74, 217, 36, 133, 0, 175, 23, 23, 79, 11, 76, 77, 118, 65, 165, 126, 38, 143, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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