Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0f6aff593e07a2c09554f98827bf6e5a4946d5aaf8aa03ff309bbe6b83d1361

Tx prefix hash: 4204af40130909792a3a4566bcc4c5ba1c616c0bd9cf0b58f274a8036aee5087
Tx public key: 43b8e02c8d0d8afd7a1fc0e786ab6982ad0c5b752f24cbcccd1fe48b19130908
Timestamp: 1578162244 Timestamp [UCT]: 2020-01-04 18:24:04 Age [y:d:h:m:s]: 04:360:06:22:40
Block: 38720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1146649 RingCT/type: yes/0
Extra: 0143b8e02c8d0d8afd7a1fc0e786ab6982ad0c5b752f24cbcccd1fe48b19130908021100000021391a8d0e000000000000000000

1 output(s) for total of 456.778249740000 dcy

stealth address amount amount idx
00: 394fc9bba39d3a47ed8292cb2fc84ca9b750e7fbe948782c50a82318a6175f8e 456.778249740000 66220 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": 38730, "vin": [ { "gen": { "height": 38720 } } ], "vout": [ { "amount": 456778249740, "target": { "key": "394fc9bba39d3a47ed8292cb2fc84ca9b750e7fbe948782c50a82318a6175f8e" } } ], "extra": [ 1, 67, 184, 224, 44, 141, 13, 138, 253, 122, 31, 192, 231, 134, 171, 105, 130, 173, 12, 91, 117, 47, 36, 203, 204, 205, 31, 228, 139, 25, 19, 9, 8, 2, 17, 0, 0, 0, 33, 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