Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8e7135eac0f24925aa191fd8b94a5f816d5b633323657df3ecc05ffacb6c728

Tx prefix hash: 6d1f4ac5a91cb7a18485d1f0fe3fe0b6629874f1bdb613592c28129074d8206a
Tx public key: bc7132551d2bc4d64e4ad6bdef1b1f7b18b9296c3d21d03e155d88d5f9baaca4
Timestamp: 1711629214 Timestamp [UCT]: 2024-03-28 12:33:34 Age [y:d:h:m:s]: 01:010:06:28:54
Block: 988169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268288 RingCT/type: yes/0
Extra: 01bc7132551d2bc4d64e4ad6bdef1b1f7b18b9296c3d21d03e155d88d5f9baaca402110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f5915112eddcfdd9e811a93ebecfd10bfb50e6c20b88d6645e32bbc355415b7 0.600000000000 1448436 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": 988179, "vin": [ { "gen": { "height": 988169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f5915112eddcfdd9e811a93ebecfd10bfb50e6c20b88d6645e32bbc355415b7" } } ], "extra": [ 1, 188, 113, 50, 85, 29, 43, 196, 214, 78, 74, 214, 189, 239, 27, 31, 123, 24, 185, 41, 108, 61, 33, 208, 62, 21, 93, 136, 213, 249, 186, 172, 164, 2, 17, 0, 0, 0, 5, 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