Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67bce2e699051d57d4dea01d45c3ad13ebcf7856de7a96dc9056d9f4400a245f

Tx prefix hash: 440f9b35128208fe21431f6001cff53d0393c6de10a37f4013f7e366490688f5
Tx public key: 1b70bf6a6ce08e5dc022e4d95bf86eee627addb90840625ead598c23d3cc8eb6
Timestamp: 1579194559 Timestamp [UCT]: 2020-01-16 17:09:19 Age [y:d:h:m:s]: 04:294:11:11:21
Block: 46970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1099867 RingCT/type: yes/0
Extra: 011b70bf6a6ce08e5dc022e4d95bf86eee627addb90840625ead598c23d3cc8eb60211000000044943cd9f000000000000000000

1 output(s) for total of 428.913513261000 dcy

stealth address amount amount idx
00: 016bb396df3701d28467067d13942d0b5aeb34e639b2d7d2e854594e78db85d9 428.913513261000 86670 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": 46980, "vin": [ { "gen": { "height": 46970 } } ], "vout": [ { "amount": 428913513261, "target": { "key": "016bb396df3701d28467067d13942d0b5aeb34e639b2d7d2e854594e78db85d9" } } ], "extra": [ 1, 27, 112, 191, 106, 108, 224, 142, 93, 192, 34, 228, 217, 91, 248, 110, 238, 98, 122, 221, 185, 8, 64, 98, 94, 173, 89, 140, 35, 211, 204, 142, 182, 2, 17, 0, 0, 0, 4, 73, 67, 205, 159, 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