Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30fb84f19e5de5e219a1848b67e41ad49929c62cce13f98c450d556472b431e4

Tx prefix hash: 119e69939c2814767ee0074f594b71df96db81d1cb4e3c25b555b31da3fdd465
Tx public key: 88d5cdf482035559c5cabd7346d1394b7953dde1c91f11fd93b0e9d1637b290d
Timestamp: 1706251014 Timestamp [UCT]: 2024-01-26 06:36:54 Age [y:d:h:m:s]: 01:287:18:02:44
Block: 943539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464468 RingCT/type: yes/0
Extra: 0188d5cdf482035559c5cabd7346d1394b7953dde1c91f11fd93b0e9d1637b290d0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae730a4b5ea3e170d52089315a1cece111c245c4eb86b7e8dd45c4e90cbd0aa9 0.600000000000 1401747 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": 943549, "vin": [ { "gen": { "height": 943539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae730a4b5ea3e170d52089315a1cece111c245c4eb86b7e8dd45c4e90cbd0aa9" } } ], "extra": [ 1, 136, 213, 205, 244, 130, 3, 85, 89, 197, 202, 189, 115, 70, 209, 57, 75, 121, 83, 221, 225, 201, 31, 17, 253, 147, 176, 233, 209, 99, 123, 41, 13, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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