Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6174b69ca2916b6cd0974adbd97c72abc815859b4b779c8c55f27d7ea16c631

Tx prefix hash: a3c688d5d6832522aa10c933748be2839a48b9bc23ea61e827abc064f743198c
Tx public key: de4ce832838cdedf85572dfedab0d9369058289c93bfc07063bfcf813a50fd33
Timestamp: 1579272482 Timestamp [UCT]: 2020-01-17 14:48:02 Age [y:d:h:m:s]: 05:115:06:25:44
Block: 47654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1232479 RingCT/type: yes/0
Extra: 01de4ce832838cdedf85572dfedab0d9369058289c93bfc07063bfcf813a50fd33021100000002391a8d0e000000000000000000

1 output(s) for total of 426.681047197000 dcy

stealth address amount amount idx
00: ea7060eb7e785029aa9862428b6c1276b9f8f1cd7c8ba881b002a7ecbc3a29fb 426.681047197000 88042 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": 47664, "vin": [ { "gen": { "height": 47654 } } ], "vout": [ { "amount": 426681047197, "target": { "key": "ea7060eb7e785029aa9862428b6c1276b9f8f1cd7c8ba881b002a7ecbc3a29fb" } } ], "extra": [ 1, 222, 76, 232, 50, 131, 140, 222, 223, 133, 87, 45, 254, 218, 176, 217, 54, 144, 88, 40, 156, 147, 191, 192, 112, 99, 191, 207, 129, 58, 80, 253, 51, 2, 17, 0, 0, 0, 2, 57, 26, 141, 14, 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