Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ce734873eb63412379f2f418f6555ce4859a77072b987c98e818cc02863ce5e

Tx prefix hash: bb6622f8caf3214a0067805b5b69f8f1c558ab97ca77be2f336a21fbc3f62192
Tx public key: d7ee55d1f91e3b856814a250d26e635062a76fb9f80e1dca0b173d8c255bc2af
Timestamp: 1703101124 Timestamp [UCT]: 2023-12-20 19:38:44 Age [y:d:h:m:s]: 01:118:20:00:35
Block: 917476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346035 RingCT/type: yes/0
Extra: 01d7ee55d1f91e3b856814a250d26e635062a76fb9f80e1dca0b173d8c255bc2af021100000001bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11c82bc8cc5b85ec1bbd73b69b15ee67c4fc90f50459ab715c0bd8e26264e9b7 0.600000000000 1375058 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": 917486, "vin": [ { "gen": { "height": 917476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11c82bc8cc5b85ec1bbd73b69b15ee67c4fc90f50459ab715c0bd8e26264e9b7" } } ], "extra": [ 1, 215, 238, 85, 209, 249, 30, 59, 133, 104, 20, 162, 80, 210, 110, 99, 80, 98, 167, 111, 185, 248, 14, 29, 202, 11, 23, 61, 140, 37, 91, 194, 175, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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