Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfbaafefe31b6eb04fe3e694d3dae0c9637f94f0a9c5c2d5d88ae71e14fb43bd

Tx prefix hash: 7b769af75a37718728690ab62d0fe01b1ef15a55edcc18ad30b98df18ad20710
Tx public key: 5914a1b999f3ad64795860fc27489ec784a983d2a1a04427602afcb82aab574a
Timestamp: 1583638283 Timestamp [UCT]: 2020-03-08 03:31:23 Age [y:d:h:m:s]: 05:238:18:57:14
Block: 78467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1323757 RingCT/type: yes/0
Extra: 015914a1b999f3ad64795860fc27489ec784a983d2a1a04427602afcb82aab574a0211000000018e602c4c000000000000000000

1 output(s) for total of 337.292782404000 dcy

stealth address amount amount idx
00: 9801f6cdb9a402f8d59cf8ce52381268fa58d8aa704cf8423b37e3083658ab8d 337.292782404000 143923 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": 78477, "vin": [ { "gen": { "height": 78467 } } ], "vout": [ { "amount": 337292782404, "target": { "key": "9801f6cdb9a402f8d59cf8ce52381268fa58d8aa704cf8423b37e3083658ab8d" } } ], "extra": [ 1, 89, 20, 161, 185, 153, 243, 173, 100, 121, 88, 96, 252, 39, 72, 158, 199, 132, 169, 131, 210, 161, 160, 68, 39, 96, 42, 252, 184, 42, 171, 87, 74, 2, 17, 0, 0, 0, 1, 142, 96, 44, 76, 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