Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67b8d1c29b90aaf2acecba16ebc4d0448075d2e4a2dedcc41667d537c04da5dc

Tx prefix hash: 1c5ed9a02c6ca573851458861e20937c2707c4a125946e4c307f8ab30172acbe
Tx public key: 0a471e9c0f79aaebcc5f44e0d9afe87c2a05914aa82dba5eb728aca1107b7970
Timestamp: 1730012496 Timestamp [UCT]: 2024-10-27 07:01:36 Age [y:d:h:m:s]: 00:027:20:23:58
Block: 1140530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19888 RingCT/type: yes/0
Extra: 010a471e9c0f79aaebcc5f44e0d9afe87c2a05914aa82dba5eb728aca1107b7970021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4874a1c15efc09587fb88545aa9210f274045d1a179deb73cd18f22383a4a7a 0.600000000000 1624331 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": 1140540, "vin": [ { "gen": { "height": 1140530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4874a1c15efc09587fb88545aa9210f274045d1a179deb73cd18f22383a4a7a" } } ], "extra": [ 1, 10, 71, 30, 156, 15, 121, 170, 235, 204, 95, 68, 224, 217, 175, 232, 124, 42, 5, 145, 74, 168, 45, 186, 94, 183, 40, 172, 161, 16, 123, 121, 112, 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