Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1e708a2ac09b7695a49cf56bdb38e8fd69271ff8ced1ce86313b3019c0faaa0

Tx prefix hash: 1c6bb2e169d94c0b3f55db796cdac6ec4b5c0e2514ae22b2b45f95237691a4d2
Tx public key: bb08d2db47920182b311a91092c2290470b84986f7022f0e770ce95fb716fa50
Timestamp: 1577019961 Timestamp [UCT]: 2019-12-22 13:06:01 Age [y:d:h:m:s]: 04:344:03:20:40
Block: 29634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1134755 RingCT/type: yes/0
Extra: 01bb08d2db47920182b311a91092c2290470b84986f7022f0e770ce95fb716fa50021100000007d81c26c0000000000000000000

1 output(s) for total of 489.601943919000 dcy

stealth address amount amount idx
00: 9eaedd30923cc05902d42c8b9a30edf987bfefaa7ebb11afcfcc83d7b87d6294 489.601943919000 48764 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": 29644, "vin": [ { "gen": { "height": 29634 } } ], "vout": [ { "amount": 489601943919, "target": { "key": "9eaedd30923cc05902d42c8b9a30edf987bfefaa7ebb11afcfcc83d7b87d6294" } } ], "extra": [ 1, 187, 8, 210, 219, 71, 146, 1, 130, 179, 17, 169, 16, 146, 194, 41, 4, 112, 184, 73, 134, 247, 2, 47, 14, 119, 12, 233, 95, 183, 22, 250, 80, 2, 17, 0, 0, 0, 7, 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