Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbf48094986d115df142577ec78ec96c7c59263a3eb72fa3a32b6999b9636e6e

Tx prefix hash: 44b8b271a2cf845fa2d70df48f8e993a8ebb6775a1e56d99ac2d81c03699a5d0
Tx public key: 600bc4ce2b4d8129bfeae444877bf88dfe53cf74bfe890df60fd8f6f02123226
Timestamp: 1581822009 Timestamp [UCT]: 2020-02-16 03:00:09 Age [y:d:h:m:s]: 05:026:15:09:29
Block: 65784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1172073 RingCT/type: yes/0
Extra: 01600bc4ce2b4d8129bfeae444877bf88dfe53cf74bfe890df60fd8f6f02123226021100000004c71d3ff9000000000000000000

1 output(s) for total of 371.561844064000 dcy

stealth address amount amount idx
00: c299166ad4ede1d78ecce4382aa5b29ad100444a366e784b9c1937dc4a0cefda 371.561844064000 121375 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": 65794, "vin": [ { "gen": { "height": 65784 } } ], "vout": [ { "amount": 371561844064, "target": { "key": "c299166ad4ede1d78ecce4382aa5b29ad100444a366e784b9c1937dc4a0cefda" } } ], "extra": [ 1, 96, 11, 196, 206, 43, 77, 129, 41, 191, 234, 228, 68, 135, 123, 248, 141, 254, 83, 207, 116, 191, 232, 144, 223, 96, 253, 143, 111, 2, 18, 50, 38, 2, 17, 0, 0, 0, 4, 199, 29, 63, 249, 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