Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b56d917cc41532733a9b7e1de6bab964a2dab22500294c972035e8b9f634c0b

Tx prefix hash: 1a197d4428c30383e37d7d045d371322a1f2f593f1a4602f1fced31690564915
Tx public key: 74e65f6e0c67cebc82bc3efdd4e946dbc5bf66992c321a08471c787f062804b6
Timestamp: 1704609446 Timestamp [UCT]: 2024-01-07 06:37:26 Age [y:d:h:m:s]: 01:018:02:07:22
Block: 929934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274234 RingCT/type: yes/0
Extra: 0174e65f6e0c67cebc82bc3efdd4e946dbc5bf66992c321a08471c787f062804b602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 754e0443cf69eaeefd42e8be13f49ee1ad8b7b05b02d0c2f85c4c28a1284b83e 0.600000000000 1387812 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": 929944, "vin": [ { "gen": { "height": 929934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "754e0443cf69eaeefd42e8be13f49ee1ad8b7b05b02d0c2f85c4c28a1284b83e" } } ], "extra": [ 1, 116, 230, 95, 110, 12, 103, 206, 188, 130, 188, 62, 253, 212, 233, 70, 219, 197, 191, 102, 153, 44, 50, 26, 8, 71, 28, 120, 127, 6, 40, 4, 182, 2, 17, 0, 0, 0, 1, 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