Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb4a290cf8d4a0291e0048e1510e209e9fb336042ffb5c94fe3b97e8b625b790

Tx prefix hash: 2bf8ce5dcd98b79460e36c49ecfa1a7b590b466a6dc45700652653e5a83c6cdb
Tx public key: f99d0cdb3c4b9f5e26e195fb2027112e174ab079ef45bdc890154493d9d06479
Timestamp: 1577651449 Timestamp [UCT]: 2019-12-29 20:30:49 Age [y:d:h:m:s]: 05:066:08:39:47
Block: 34537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1197190 RingCT/type: yes/0
Extra: 01f99d0cdb3c4b9f5e26e195fb2027112e174ab079ef45bdc890154493d9d064790211000000088a2ee0d9000000000000000000

1 output(s) for total of 471.590923300000 dcy

stealth address amount amount idx
00: 64cd0f4f6ee7228069569cd60e06fe4f0bbbd123040310d3ad4e41fcbe350870 471.590923300000 58133 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": 34547, "vin": [ { "gen": { "height": 34537 } } ], "vout": [ { "amount": 471590923300, "target": { "key": "64cd0f4f6ee7228069569cd60e06fe4f0bbbd123040310d3ad4e41fcbe350870" } } ], "extra": [ 1, 249, 157, 12, 219, 60, 75, 159, 94, 38, 225, 149, 251, 32, 39, 17, 46, 23, 74, 176, 121, 239, 69, 189, 200, 144, 21, 68, 147, 217, 208, 100, 121, 2, 17, 0, 0, 0, 8, 138, 46, 224, 217, 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