Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ec89d6e606bcb3abae3d77e2bc00bc4c8576bea62fb01d7716145b1f6378022

Tx prefix hash: 2e2c877de7b3af8de6e5d58a5cae4918e7c1feb6bcd53dbecfe3b37de52c9c5c
Tx public key: 3a187a38e4f36ba9725dd7b7ab413d378c8b3de95ea8d2eb87308629b9806b79
Timestamp: 1578076328 Timestamp [UCT]: 2020-01-03 18:32:08 Age [y:d:h:m:s]: 05:000:01:45:52
Block: 37902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150194 RingCT/type: yes/0
Extra: 013a187a38e4f36ba9725dd7b7ab413d378c8b3de95ea8d2eb87308629b9806b79021100000011d81c26c0000000000000000000

1 output(s) for total of 459.637856680000 dcy

stealth address amount amount idx
00: b585d4399ce373cbb770239a469a43dae1380f6377efa276d35c89e1e109ffd1 459.637856680000 64447 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": 37912, "vin": [ { "gen": { "height": 37902 } } ], "vout": [ { "amount": 459637856680, "target": { "key": "b585d4399ce373cbb770239a469a43dae1380f6377efa276d35c89e1e109ffd1" } } ], "extra": [ 1, 58, 24, 122, 56, 228, 243, 107, 169, 114, 93, 215, 183, 171, 65, 61, 55, 140, 139, 61, 233, 94, 168, 210, 235, 135, 48, 134, 41, 185, 128, 107, 121, 2, 17, 0, 0, 0, 17, 216, 28, 38, 192, 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