Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd99e5615f9c5856df88ba2029c1cb2876aaff57b16d77862c778ebd1d5e8995

Tx prefix hash: 556a559ea9dd72eeb6e00e60cf2b2b13f2bb375a78f9798119fd5d54bc9b5ead
Tx public key: 8f3e66f559927778408344ab89dd84fc74ea8b9e874510dd8b14a16868c47a00
Timestamp: 1700602242 Timestamp [UCT]: 2023-11-21 21:30:42 Age [y:d:h:m:s]: 01:189:09:25:38
Block: 896731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396593 RingCT/type: yes/0
Extra: 018f3e66f559927778408344ab89dd84fc74ea8b9e874510dd8b14a16868c47a00021100000001faf35c9c000000000000000000

1 output(s) for total of 0.655779648000 dcy

stealth address amount amount idx
00: 209a9e5f3b02fc5b8ceb6ae62280e4a554b082dda66b1ee4d240f49834e36fd0 0.655779648000 1353072 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": 896741, "vin": [ { "gen": { "height": 896731 } } ], "vout": [ { "amount": 655779648, "target": { "key": "209a9e5f3b02fc5b8ceb6ae62280e4a554b082dda66b1ee4d240f49834e36fd0" } } ], "extra": [ 1, 143, 62, 102, 245, 89, 146, 119, 120, 64, 131, 68, 171, 137, 221, 132, 252, 116, 234, 139, 158, 135, 69, 16, 221, 139, 20, 161, 104, 104, 196, 122, 0, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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