Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e711da5dc214ae51870944682b65a3d624397acb3b9650de701877a55a604039

Tx prefix hash: e4e3247f2e621bd5b8c3879ba0ad3137064606f1ed0678d4b9e9af3c93687475
Tx public key: 268c38307229c00e53e66d39d488a63894abaa31aede3162cb2a39a54a21a598
Timestamp: 1576427386 Timestamp [UCT]: 2019-12-15 16:29:46 Age [y:d:h:m:s]: 05:052:22:17:34
Block: 27815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184170 RingCT/type: yes/0
Extra: 01268c38307229c00e53e66d39d488a63894abaa31aede3162cb2a39a54a21a59802110000001ead433a0b000000000000000000

1 output(s) for total of 496.407373687000 dcy

stealth address amount amount idx
00: b0e148129dd79eb267c7d09a03f4de1d0ba2c9e130e0ddbc4c392bb97d5dd093 496.407373687000 45871 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": 27825, "vin": [ { "gen": { "height": 27815 } } ], "vout": [ { "amount": 496407373687, "target": { "key": "b0e148129dd79eb267c7d09a03f4de1d0ba2c9e130e0ddbc4c392bb97d5dd093" } } ], "extra": [ 1, 38, 140, 56, 48, 114, 41, 192, 14, 83, 230, 109, 57, 212, 136, 166, 56, 148, 171, 170, 49, 174, 222, 49, 98, 203, 42, 57, 165, 74, 33, 165, 152, 2, 17, 0, 0, 0, 30, 173, 67, 58, 11, 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