Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cf642c4209d4fb6a361a1c2a32c1d020bb9fe9496db6290be3e0916c7b18ff1

Tx prefix hash: 52e552c4bbb2b379d2df5080a5d7fafef79fe472c0fabc603892930bfa8932a7
Tx public key: 1d6d4fdcafeb8e9b502dc808f3570607d281d342fc11b3beac80e7000f1ed8f1
Timestamp: 1732260058 Timestamp [UCT]: 2024-11-22 07:20:58 Age [y:d:h:m:s]: 00:002:00:35:35
Block: 1159096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1454 RingCT/type: yes/0
Extra: 011d6d4fdcafeb8e9b502dc808f3570607d281d342fc11b3beac80e7000f1ed8f1021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d58a61d8c791a6f11fed38c8ad5de27c3cdcdf71b5c86fa0a564ec15453ea47d 0.600000000000 1644727 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": 1159106, "vin": [ { "gen": { "height": 1159096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d58a61d8c791a6f11fed38c8ad5de27c3cdcdf71b5c86fa0a564ec15453ea47d" } } ], "extra": [ 1, 29, 109, 79, 220, 175, 235, 142, 155, 80, 45, 200, 8, 243, 87, 6, 7, 210, 129, 211, 66, 252, 17, 179, 190, 172, 128, 231, 0, 15, 30, 216, 241, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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