Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9840abf609b6014b5138866a33391ec7933d4bea295a3897da82bc1ffddc664a

Tx prefix hash: f8fb5020566480228d8d757ff38f93e9eb4a9f18f565065cf36b5d96f9a252f6
Tx public key: 32c095e5c154b81805f916b4aaa64d7db1ebf8fb3c6336b8b93f8ffd28843a2f
Timestamp: 1728741036 Timestamp [UCT]: 2024-10-12 13:50:36 Age [y:d:h:m:s]: 00:026:10:54:58
Block: 1130026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18864 RingCT/type: yes/0
Extra: 0132c095e5c154b81805f916b4aaa64d7db1ebf8fb3c6336b8b93f8ffd28843a2f021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4816d4451136f7d9a91cb80523616397dfba697baacf720c566b76502d16d1cf 0.600000000000 1612897 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": 1130036, "vin": [ { "gen": { "height": 1130026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4816d4451136f7d9a91cb80523616397dfba697baacf720c566b76502d16d1cf" } } ], "extra": [ 1, 50, 192, 149, 229, 193, 84, 184, 24, 5, 249, 22, 180, 170, 166, 77, 125, 177, 235, 248, 251, 60, 99, 54, 184, 185, 63, 143, 253, 40, 132, 58, 47, 2, 17, 0, 0, 0, 2, 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