Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2daff1bd0e7693c29b2edd12540bf0e73fc89805b884e418bb49369d8523e5cc

Tx prefix hash: 9e0dfc950a25c0e39bc3008facb4bb896c3644358d5f5b07d3d96241f53bc1b6
Tx public key: b5578a808d6a59d8d393179b0ef2aa692d428cfc9c3fc1d4198c6dff0029609a
Timestamp: 1709401860 Timestamp [UCT]: 2024-03-02 17:51:00 Age [y:d:h:m:s]: 01:036:01:21:50
Block: 969706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286753 RingCT/type: yes/0
Extra: 01b5578a808d6a59d8d393179b0ef2aa692d428cfc9c3fc1d4198c6dff0029609a02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b6453fdbdb9b04a5f7adea314474b521113cb598c34df61aa4cf62f888f7118 0.600000000000 1429543 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": 969716, "vin": [ { "gen": { "height": 969706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b6453fdbdb9b04a5f7adea314474b521113cb598c34df61aa4cf62f888f7118" } } ], "extra": [ 1, 181, 87, 138, 128, 141, 106, 89, 216, 211, 147, 23, 155, 14, 242, 170, 105, 45, 66, 140, 252, 156, 63, 193, 212, 25, 140, 109, 255, 0, 41, 96, 154, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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