Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2732f9ad13ddc55f765e38d7b8e9d3bc4b31550dd3730852e5d34c59bf900877

Tx prefix hash: cf12b5fd0a41cc5ac244c97ca2c4f6ced27f8e133aaafeb805b87616b42304e8
Tx public key: 686ff9a07533d4cff607ff75976535e1a58a454239fee87afdc0f6af24692899
Timestamp: 1693350119 Timestamp [UCT]: 2023-08-29 23:01:59 Age [y:d:h:m:s]: 01:078:14:02:30
Block: 836795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317465 RingCT/type: yes/0
Extra: 01686ff9a07533d4cff607ff75976535e1a58a454239fee87afdc0f6af2469289902110000000fd4dbf7b9000000000000000000

1 output(s) for total of 1.035978806000 dcy

stealth address amount amount idx
00: 82c505879f2c989387889ce044f4fd17854ad273c2cdee0e2bee91be40200aa0 1.035978806000 1289393 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": 836805, "vin": [ { "gen": { "height": 836795 } } ], "vout": [ { "amount": 1035978806, "target": { "key": "82c505879f2c989387889ce044f4fd17854ad273c2cdee0e2bee91be40200aa0" } } ], "extra": [ 1, 104, 111, 249, 160, 117, 51, 212, 207, 246, 7, 255, 117, 151, 101, 53, 225, 165, 138, 69, 66, 57, 254, 232, 122, 253, 192, 246, 175, 36, 105, 40, 153, 2, 17, 0, 0, 0, 15, 212, 219, 247, 185, 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