Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52d6ce7534a0b999cf9c40cf466810f4b7680d678016ff362f1743e07338144d

Tx prefix hash: fba158eb6bb8550c80d8e1f969b39344e7f8781e372ab1a7955b3a1c3131916f
Tx public key: 8c5fdbd9781dc2221d6d7536f5dd80c0cb61dfbb116d75f8ed3c22714b17e0b9
Timestamp: 1676957137 Timestamp [UCT]: 2023-02-21 05:25:37 Age [y:d:h:m:s]: 02:100:21:03:58
Block: 701588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 593740 RingCT/type: yes/0
Extra: 018c5fdbd9781dc2221d6d7536f5dd80c0cb61dfbb116d75f8ed3c22714b17e0b902110000000374b6d784000000000000000000

1 output(s) for total of 2.906348062000 dcy

stealth address amount amount idx
00: 5f22c38c4cce16b44d2753ced0e9f0ef38b98f94c64bb2d914e9b649b196f509 2.906348062000 1145075 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": 701598, "vin": [ { "gen": { "height": 701588 } } ], "vout": [ { "amount": 2906348062, "target": { "key": "5f22c38c4cce16b44d2753ced0e9f0ef38b98f94c64bb2d914e9b649b196f509" } } ], "extra": [ 1, 140, 95, 219, 217, 120, 29, 194, 34, 29, 109, 117, 54, 245, 221, 128, 192, 203, 97, 223, 187, 17, 109, 117, 248, 237, 60, 34, 113, 75, 23, 224, 185, 2, 17, 0, 0, 0, 3, 116, 182, 215, 132, 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