Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5617b57bef4713eac3877d30582cd4f16fb06c6db259ac87fa18bc811a615172

Tx prefix hash: 30e8ad8556add5ceca17259ae171e09641b8b2219893fdd7d6ad339574d7eb5c
Tx public key: 0c2a10e8fed0a82af9f7db786f32fb4e03d7035e579248650a80ef8fba823d26
Timestamp: 1697298046 Timestamp [UCT]: 2023-10-14 15:40:46 Age [y:d:h:m:s]: 01:178:06:49:21
Block: 869541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388454 RingCT/type: yes/0
Extra: 010c2a10e8fed0a82af9f7db786f32fb4e03d7035e579248650a80ef8fba823d2602110000000133af99f4000000000000000000

1 output(s) for total of 0.806955770000 dcy

stealth address amount amount idx
00: b09affd0a74d03318729d803d24c1eabd444af2d51871b6c56cdefd2bd12a84a 0.806955770000 1324390 of 0

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": 869551, "vin": [ { "gen": { "height": 869541 } } ], "vout": [ { "amount": 806955770, "target": { "key": "b09affd0a74d03318729d803d24c1eabd444af2d51871b6c56cdefd2bd12a84a" } } ], "extra": [ 1, 12, 42, 16, 232, 254, 208, 168, 42, 249, 247, 219, 120, 111, 50, 251, 78, 3, 215, 3, 94, 87, 146, 72, 101, 10, 128, 239, 143, 186, 130, 61, 38, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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