Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2945b783c0f28a794138960b453addb887b4e32ef9e065129f75237106e5ae1

Tx prefix hash: 34128fe6bae414ee567b5daeca24cabfab0d83839df77ecbe527cd80a82cf75b
Tx public key: f4e74604cea326e3a2708754db2ae99f9035c8f94fd5d54a0bfa3d90a5aa5bc5
Timestamp: 1582443650 Timestamp [UCT]: 2020-02-23 07:40:50 Age [y:d:h:m:s]: 04:306:05:43:03
Block: 70848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111336 RingCT/type: yes/0
Extra: 01f4e74604cea326e3a2708754db2ae99f9035c8f94fd5d54a0bfa3d90a5aa5bc50211000000030aca7173000000000000000000

1 output(s) for total of 357.480180076000 dcy

stealth address amount amount idx
00: 9a0879ed016ab05e00aa9219d575b985dcf940d4fad68d68d4c61466c560e908 357.480180076000 130870 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": 70858, "vin": [ { "gen": { "height": 70848 } } ], "vout": [ { "amount": 357480180076, "target": { "key": "9a0879ed016ab05e00aa9219d575b985dcf940d4fad68d68d4c61466c560e908" } } ], "extra": [ 1, 244, 231, 70, 4, 206, 163, 38, 227, 162, 112, 135, 84, 219, 42, 233, 159, 144, 53, 200, 249, 79, 213, 213, 74, 11, 250, 61, 144, 165, 170, 91, 197, 2, 17, 0, 0, 0, 3, 10, 202, 113, 115, 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