Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14b8d0b2405c6810bd8b028e2a19b50ed447322973971436d14233cb7f34ecf5

Tx prefix hash: a25752a37632815b48b243eead2f00c5872a972a7e08c797c0c91f29ced39231
Tx public key: daee56b573a7b6683bd1aac8c286a5a473ce95dcfc2c841ff3d633995c9a18c7
Timestamp: 1733842602 Timestamp [UCT]: 2024-12-10 14:56:42 Age [y:d:h:m:s]: 00:103:23:48:10
Block: 1172222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74102 RingCT/type: yes/0
Extra: 01daee56b573a7b6683bd1aac8c286a5a473ce95dcfc2c841ff3d633995c9a18c7021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 280abb1f3ef7913d5e9675d9653449c677d75c159e36e4eb8b8ac420f264f2c1 0.600000000000 1658087 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": 1172232, "vin": [ { "gen": { "height": 1172222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "280abb1f3ef7913d5e9675d9653449c677d75c159e36e4eb8b8ac420f264f2c1" } } ], "extra": [ 1, 218, 238, 86, 181, 115, 167, 182, 104, 59, 209, 170, 200, 194, 134, 165, 164, 115, 206, 149, 220, 252, 44, 132, 31, 243, 214, 51, 153, 92, 154, 24, 199, 2, 17, 0, 0, 0, 5, 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