Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5178c5a2b2e546943aa1f4c47cbd7ef99e41879e56eff7958a8d46a973e42f2d

Tx prefix hash: bfc442a7282aa307792092b29e911ef67740a686fc5679db14a09c418085f387
Tx public key: 7ea7f73ad72f98a5613590a4f2adfb385504765649d501861f9ae0a39bed17eb
Timestamp: 1634962313 Timestamp [UCT]: 2021-10-23 04:11:53 Age [y:d:h:m:s]: 04:009:14:30:32
Block: 358568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1043547 RingCT/type: yes/0
Extra: 017ea7f73ad72f98a5613590a4f2adfb385504765649d501861f9ae0a39bed17eb02110000000537cb3088000000000000000000

1 output(s) for total of 39.802997413000 dcy

stealth address amount amount idx
00: 3c4682a83baa95b5aab166cd0d1b2407dd16026a1eec671c2c02c8acda1ece8f 39.802997413000 730561 of 0

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": 358578, "vin": [ { "gen": { "height": 358568 } } ], "vout": [ { "amount": 39802997413, "target": { "key": "3c4682a83baa95b5aab166cd0d1b2407dd16026a1eec671c2c02c8acda1ece8f" } } ], "extra": [ 1, 126, 167, 247, 58, 215, 47, 152, 165, 97, 53, 144, 164, 242, 173, 251, 56, 85, 4, 118, 86, 73, 213, 1, 134, 31, 154, 224, 163, 155, 237, 23, 235, 2, 17, 0, 0, 0, 5, 55, 203, 48, 136, 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