Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c6fe220d1840c69043901286bfedebaf762d8c4a7ebea4fd887507633f66851

Tx prefix hash: 70c7db9405b0362f8bfa7ca6f70c79014d725b0a12e4287bb0f55b2c7a35985a
Tx public key: f734798ef87a5f4e81a2178c70e8f945461efb6785ab1ef1665cd1d6d86e5e3f
Timestamp: 1734462040 Timestamp [UCT]: 2024-12-17 19:00:40 Age [y:d:h:m:s]: 00:129:05:38:47
Block: 1177364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92128 RingCT/type: yes/0
Extra: 01f734798ef87a5f4e81a2178c70e8f945461efb6785ab1ef1665cd1d6d86e5e3f0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b7e116114cd3bbe5a5e1a54329d9e7930da60e826d1cb5c9a475a8a88906dbd 0.600000000000 1663735 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": 1177374, "vin": [ { "gen": { "height": 1177364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b7e116114cd3bbe5a5e1a54329d9e7930da60e826d1cb5c9a475a8a88906dbd" } } ], "extra": [ 1, 247, 52, 121, 142, 248, 122, 95, 78, 129, 162, 23, 140, 112, 232, 249, 69, 70, 30, 251, 103, 133, 171, 30, 241, 102, 92, 209, 214, 216, 110, 94, 63, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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