Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc34e470ea1ea4b231c16ac626f7aa4c65e5bd5f1dcaf6e1bf5799088bde7be9

Tx prefix hash: e87e6bc3c4d22d0713f1dd5dfc6a1cd32201e6890347b4f1f981d54460fafe0f
Tx public key: 559c8d744d16dfb3b9d9bc3e29d4cdd28b4f2ad101004a288fd5a3be364bd92c
Timestamp: 1730216150 Timestamp [UCT]: 2024-10-29 15:35:50 Age [y:d:h:m:s]: 01:023:07:55:53
Block: 1142189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275091 RingCT/type: yes/0
Extra: 01559c8d744d16dfb3b9d9bc3e29d4cdd28b4f2ad101004a288fd5a3be364bd92c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3c5984114c8cf7e28cd6ce8be580b033ee1abfc3ca81b62884fc745ca65cfbc 0.600000000000 1626032 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": 1142199, "vin": [ { "gen": { "height": 1142189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3c5984114c8cf7e28cd6ce8be580b033ee1abfc3ca81b62884fc745ca65cfbc" } } ], "extra": [ 1, 85, 156, 141, 116, 77, 22, 223, 179, 185, 217, 188, 62, 41, 212, 205, 210, 139, 79, 42, 209, 1, 0, 74, 40, 143, 213, 163, 190, 54, 75, 217, 44, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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