Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b563ef11760bc0333e8d1ecc018695cc183b7384e568e0b09f2c202eb200548

Tx prefix hash: 5247017459f7699f31c5527f82863b991d325c5068e73d9fe428311bf4ad3015
Tx public key: cc2aa8f15bd1da317dd1c8e410debd07e72784568f914f0a2f539a95dcf3e233
Timestamp: 1697836520 Timestamp [UCT]: 2023-10-20 21:15:20 Age [y:d:h:m:s]: 01:164:06:00:35
Block: 874019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378387 RingCT/type: yes/0
Extra: 01cc2aa8f15bd1da317dd1c8e410debd07e72784568f914f0a2f539a95dcf3e23302110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.779852111000 dcy

stealth address amount amount idx
00: 69cd07f895854316a217d9989c04506596820dc80c565af6e455b2cf7c6d0513 0.779852111000 1329211 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": 874029, "vin": [ { "gen": { "height": 874019 } } ], "vout": [ { "amount": 779852111, "target": { "key": "69cd07f895854316a217d9989c04506596820dc80c565af6e455b2cf7c6d0513" } } ], "extra": [ 1, 204, 42, 168, 241, 91, 209, 218, 49, 125, 209, 200, 228, 16, 222, 189, 7, 231, 39, 132, 86, 143, 145, 79, 10, 47, 83, 154, 149, 220, 243, 226, 51, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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