Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f44a920d3c1d5c666ff0e782e017495ade2b08d6e43106bdbb6d35c6760840b

Tx prefix hash: f5d1065f3403627c371869ca8f98668accf93ec6775c22e625a9b37a0575b653
Tx public key: e956a7e1d8d7c2eae2e40df1234e0ef485bbcf06f9b91b5d1c6aa4f681fce623
Timestamp: 1702708605 Timestamp [UCT]: 2023-12-16 06:36:45 Age [y:d:h:m:s]: 01:340:16:10:31
Block: 914199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502341 RingCT/type: yes/0
Extra: 01e956a7e1d8d7c2eae2e40df1234e0ef485bbcf06f9b91b5d1c6aa4f681fce62302110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81a5d652ad832ff9a679558c72a67fce3429cc3e635cb21f6849d1128539773d 0.600000000000 1371485 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": 914209, "vin": [ { "gen": { "height": 914199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81a5d652ad832ff9a679558c72a67fce3429cc3e635cb21f6849d1128539773d" } } ], "extra": [ 1, 233, 86, 167, 225, 216, 215, 194, 234, 226, 228, 13, 241, 35, 78, 14, 244, 133, 187, 207, 6, 249, 185, 27, 93, 28, 106, 164, 246, 129, 252, 230, 35, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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