Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c60c2be4f4c727273cad2d7465cae6b7ed600a251d566a31d5f81664ac7c061

Tx prefix hash: f21341530377158128f5469f1d670b65d80746ebc50d066902ec4d2a16a1224c
Tx public key: 1f9215f07b98afda81681412381823b21f31ca01c18e984e8f1229184781d56c
Timestamp: 1734864064 Timestamp [UCT]: 2024-12-22 10:41:04 Age [y:d:h:m:s]: 00:177:08:33:39
Block: 1180698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126451 RingCT/type: yes/0
Extra: 011f9215f07b98afda81681412381823b21f31ca01c18e984e8f1229184781d56c02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3224fe9c8b66f8ada0832c8a28432e7ca0cc88ae7625f1a8002747b9d1ae50be 0.600000000000 1667111 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": 1180708, "vin": [ { "gen": { "height": 1180698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3224fe9c8b66f8ada0832c8a28432e7ca0cc88ae7625f1a8002747b9d1ae50be" } } ], "extra": [ 1, 31, 146, 21, 240, 123, 152, 175, 218, 129, 104, 20, 18, 56, 24, 35, 178, 31, 49, 202, 1, 193, 142, 152, 78, 143, 18, 41, 24, 71, 129, 213, 108, 2, 17, 0, 0, 0, 10, 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