Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b2d94b92371741e2a3f5fc73c74c384bcefb3e1c002c4c000acb319ef80ffd7

Tx prefix hash: b34f36077486d186d0611089998b8c4b5bd98c1ffbe5de422ab189ab4baa63b8
Tx public key: ec4d82e65999bd1f9f76b74a17dc87a451803d64bddcde0d5cf05310e83886e1
Timestamp: 1702256044 Timestamp [UCT]: 2023-12-11 00:54:04 Age [y:d:h:m:s]: 01:140:23:24:52
Block: 910447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361920 RingCT/type: yes/0
Extra: 01ec4d82e65999bd1f9f76b74a17dc87a451803d64bddcde0d5cf05310e83886e102110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5a549aaea110a643b4accf683aee6b5db76d4b49533c8ed07e49e566630f861 0.600000000000 1367604 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": 910457, "vin": [ { "gen": { "height": 910447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5a549aaea110a643b4accf683aee6b5db76d4b49533c8ed07e49e566630f861" } } ], "extra": [ 1, 236, 77, 130, 230, 89, 153, 189, 31, 159, 118, 183, 74, 23, 220, 135, 164, 81, 128, 61, 100, 189, 220, 222, 13, 92, 240, 83, 16, 232, 56, 134, 225, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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