Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae511dc68767ea665899f286b5de0982a6c40e36e5708633eaa5f1a78a80e7f6

Tx prefix hash: 3a8ed55e2d670ebe321f06651f34263e206b6c345a1644ed7c7ec47a72368d6b
Tx public key: 8ff50ec89c9f2f94ef02c84f608a91259b54fee3faaa0b9038fb7952608bc85e
Timestamp: 1721755541 Timestamp [UCT]: 2024-07-23 17:25:41 Age [y:d:h:m:s]: 00:257:10:44:52
Block: 1072099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183907 RingCT/type: yes/0
Extra: 018ff50ec89c9f2f94ef02c84f608a91259b54fee3faaa0b9038fb7952608bc85e021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bebc38c494ea436d9a25240c75fb9155ba2a7d71c4f8427336f4c5b13da9c7a 0.600000000000 1544546 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": 1072109, "vin": [ { "gen": { "height": 1072099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bebc38c494ea436d9a25240c75fb9155ba2a7d71c4f8427336f4c5b13da9c7a" } } ], "extra": [ 1, 143, 245, 14, 200, 156, 159, 47, 148, 239, 2, 200, 79, 96, 138, 145, 37, 155, 84, 254, 227, 250, 170, 11, 144, 56, 251, 121, 82, 96, 139, 200, 94, 2, 17, 0, 0, 0, 9, 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