Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c54091d6869e0f44138f9a251c108947af14d91f0d97d05bbec9f2a8a3252328

Tx prefix hash: c24f879558d58c25904cf7a73734e314f61c495a13a03c6e8c65b99e4897916e
Tx public key: 824b7cd2d5306d6bc4a1be1afb03f8beae2fe240414034f983c640ff7e0577e8
Timestamp: 1577787795 Timestamp [UCT]: 2019-12-31 10:23:15 Age [y:d:h:m:s]: 05:065:03:08:59
Block: 35634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196354 RingCT/type: yes/0
Extra: 01824b7cd2d5306d6bc4a1be1afb03f8beae2fe240414034f983c640ff7e0577e80211000000a9c3a1a09f000000000000000000

1 output(s) for total of 467.660424625000 dcy

stealth address amount amount idx
00: 712d9c6eef9d3ce70f7cd4a0c838226f74d1520323e35a4c35258f0fc23e0ff2 467.660424625000 60141 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": 35644, "vin": [ { "gen": { "height": 35634 } } ], "vout": [ { "amount": 467660424625, "target": { "key": "712d9c6eef9d3ce70f7cd4a0c838226f74d1520323e35a4c35258f0fc23e0ff2" } } ], "extra": [ 1, 130, 75, 124, 210, 213, 48, 109, 107, 196, 161, 190, 26, 251, 3, 248, 190, 174, 47, 226, 64, 65, 64, 52, 249, 131, 198, 64, 255, 126, 5, 119, 232, 2, 17, 0, 0, 0, 169, 195, 161, 160, 159, 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