Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0397b54518c44e029270e5db8cc2a661d26cdce039525487bedb340c320b6f8d

Tx prefix hash: 86adacb5c34dcae7d02ce67837ee82ac4a0a8b1efe1059f56e0a87825b5256cd
Tx public key: e2d7cd1143d9084c7e4263e5a89406ec620877a4b7528a600a3f8ef20c8b915b
Timestamp: 1731349564 Timestamp [UCT]: 2024-11-11 18:26:04 Age [y:d:h:m:s]: 00:173:11:54:36
Block: 1151551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123847 RingCT/type: yes/0
Extra: 01e2d7cd1143d9084c7e4263e5a89406ec620877a4b7528a600a3f8ef20c8b915b0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2975d72e861c527d099aaa351c172ede8f147b6eb381e0e640f1c573c6115ec 0.600000000000 1637106 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": 1151561, "vin": [ { "gen": { "height": 1151551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2975d72e861c527d099aaa351c172ede8f147b6eb381e0e640f1c573c6115ec" } } ], "extra": [ 1, 226, 215, 205, 17, 67, 217, 8, 76, 126, 66, 99, 229, 168, 148, 6, 236, 98, 8, 119, 164, 183, 82, 138, 96, 10, 63, 142, 242, 12, 139, 145, 91, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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