Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db39b02c3b5d5f64a34f671f411a7709410cfdc9e3d3eea766c370c2a0c93f76

Tx prefix hash: dd051fbf1b2e6610a5fc8e7ab8f9324eae5faf53d3863a459eff8901af2f8113
Tx public key: 3f91119a7b53a007d330b60bb4cbac32b9d85c26f690a21e45575223b122da0f
Timestamp: 1719091834 Timestamp [UCT]: 2024-06-22 21:30:34 Age [y:d:h:m:s]: 00:305:14:59:04
Block: 1050008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218426 RingCT/type: yes/0
Extra: 013f91119a7b53a007d330b60bb4cbac32b9d85c26f690a21e45575223b122da0f021100000010c5f9cfd0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5781931ce79497379935d3c5a17320a59cb486686b9d54e891433875a80b2dde 0.600000000000 1520147 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": 1050018, "vin": [ { "gen": { "height": 1050008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5781931ce79497379935d3c5a17320a59cb486686b9d54e891433875a80b2dde" } } ], "extra": [ 1, 63, 145, 17, 154, 123, 83, 160, 7, 211, 48, 182, 11, 180, 203, 172, 50, 185, 216, 92, 38, 246, 144, 162, 30, 69, 87, 82, 35, 177, 34, 218, 15, 2, 17, 0, 0, 0, 16, 197, 249, 207, 208, 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