Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2922dfa4ca733c3cc4b5b96919fea458608770f3e389505f5617fcff78c6730e

Tx prefix hash: 06f0723812fe073c714646cb74e90f5b7dd72efcf5af2c09251dd19fcde43134
Tx public key: bc256056f6febd208537cb93c9c47ec6985bdef961c1bfbd7e91d1d0542a2976
Timestamp: 1717331575 Timestamp [UCT]: 2024-06-02 12:32:55 Age [y:d:h:m:s]: 01:000:20:51:54
Block: 1035447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261523 RingCT/type: yes/0
Extra: 01bc256056f6febd208537cb93c9c47ec6985bdef961c1bfbd7e91d1d0542a29760211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbcd6e35a59cacf0bc1575a3c9fd53b3a97b18df387b76757aea3a6d94ff246d 0.600000000000 1503968 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": 1035457, "vin": [ { "gen": { "height": 1035447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbcd6e35a59cacf0bc1575a3c9fd53b3a97b18df387b76757aea3a6d94ff246d" } } ], "extra": [ 1, 188, 37, 96, 86, 246, 254, 189, 32, 133, 55, 203, 147, 201, 196, 126, 198, 152, 91, 222, 249, 97, 193, 191, 189, 126, 145, 209, 208, 84, 42, 41, 118, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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