Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a65dba335ce721319cb1efe2f06f25f415c901ba6ec665fec00cd401a26a845

Tx prefix hash: 7081ae5b2bd925db0099731cdb70f3a507fd73c1711367699940905fb29c15c2
Tx public key: 3e71f5ecb6ae64791484c2ae355d3bbc40b0d979c390743eed9db33bd387ea7a
Timestamp: 1700836892 Timestamp [UCT]: 2023-11-24 14:41:32 Age [y:d:h:m:s]: 01:179:06:35:11
Block: 898680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389341 RingCT/type: yes/0
Extra: 013e71f5ecb6ae64791484c2ae355d3bbc40b0d979c390743eed9db33bd387ea7a02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.646100512000 dcy

stealth address amount amount idx
00: cf7ff44ea889a74bf0bad72756e051a33f14e474ab95dcdc314c6992aaa2c2cb 0.646100512000 1355111 of 0

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": 898690, "vin": [ { "gen": { "height": 898680 } } ], "vout": [ { "amount": 646100512, "target": { "key": "cf7ff44ea889a74bf0bad72756e051a33f14e474ab95dcdc314c6992aaa2c2cb" } } ], "extra": [ 1, 62, 113, 245, 236, 182, 174, 100, 121, 20, 132, 194, 174, 53, 93, 59, 188, 64, 176, 217, 121, 195, 144, 116, 62, 237, 157, 179, 59, 211, 135, 234, 122, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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