Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 340baa724a2ff94de0791d25b498f7bfb37df487dc23604770cbd34103f9c490

Tx prefix hash: 530305a30469ac2ac17fa9508c910a8ac166c2f2e86fede8f9db7247d2d09a8b
Tx public key: ecd0e8b41f2061f0a95f4d887a81393ed03a1b85d275aec53dca509b511ef965
Timestamp: 1728260374 Timestamp [UCT]: 2024-10-07 00:19:34 Age [y:d:h:m:s]: 00:159:22:58:46
Block: 1126041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114132 RingCT/type: yes/0
Extra: 01ecd0e8b41f2061f0a95f4d887a81393ed03a1b85d275aec53dca509b511ef96502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4e5eb0fb5c51a6a1cedcbceecfe0270d1665ec1c348de0c7e810e56187020a6 0.600000000000 1608814 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": 1126051, "vin": [ { "gen": { "height": 1126041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4e5eb0fb5c51a6a1cedcbceecfe0270d1665ec1c348de0c7e810e56187020a6" } } ], "extra": [ 1, 236, 208, 232, 180, 31, 32, 97, 240, 169, 95, 77, 136, 122, 129, 57, 62, 208, 58, 27, 133, 210, 117, 174, 197, 61, 202, 80, 155, 81, 30, 249, 101, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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