Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eb292f3d950d4c09fdf21c79aadd525e423f611b6921b0e0c2384f818f564ed

Tx prefix hash: 70adf97b089557b15b05c9afe71b9c5b64afd2c22d2ad2b77ae0b554f68d9026
Tx public key: f47dae45fe4142c8130ea71a984bc9e22733e0fbcb324503faa6127cc4b76840
Timestamp: 1712218412 Timestamp [UCT]: 2024-04-04 08:13:32 Age [y:d:h:m:s]: 01:304:00:59:51
Block: 993011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475935 RingCT/type: yes/0
Extra: 01f47dae45fe4142c8130ea71a984bc9e22733e0fbcb324503faa6127cc4b7684002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc5d7d779f1f9dfb2d849e0365f4a74806e40f5c3327dc1cc2e32045cf2b8da1 0.600000000000 1453389 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": 993021, "vin": [ { "gen": { "height": 993011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc5d7d779f1f9dfb2d849e0365f4a74806e40f5c3327dc1cc2e32045cf2b8da1" } } ], "extra": [ 1, 244, 125, 174, 69, 254, 65, 66, 200, 19, 14, 167, 26, 152, 75, 201, 226, 39, 51, 224, 251, 203, 50, 69, 3, 250, 166, 18, 124, 196, 183, 104, 64, 2, 17, 0, 0, 0, 1, 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