Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fe5cf23b47f61e47de1356d21382aadbf2bfa1831758a3e1a37dd2ac6b78f91

Tx prefix hash: 011d787527f99fe3d3b8395f2f13f1e7e9646ce08ecd54501d633015a4c7c128
Tx public key: b48ad0cc7b354132f9bbe9368796507f8029eb0b23f11ccac5efc4bac6b61fd0
Timestamp: 1636707079 Timestamp [UCT]: 2021-11-12 08:51:19 Age [y:d:h:m:s]: 03:182:15:14:50
Block: 372685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 908964 RingCT/type: yes/0
Extra: 01b48ad0cc7b354132f9bbe9368796507f8029eb0b23f11ccac5efc4bac6b61fd002110000000106faf294000000000000000000

1 output(s) for total of 35.738825537000 dcy

stealth address amount amount idx
00: fa8813c342f95fabed906e80f1444e9303818f3ff7d390069a07f95ca6b7d4d9 35.738825537000 754883 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": 372695, "vin": [ { "gen": { "height": 372685 } } ], "vout": [ { "amount": 35738825537, "target": { "key": "fa8813c342f95fabed906e80f1444e9303818f3ff7d390069a07f95ca6b7d4d9" } } ], "extra": [ 1, 180, 138, 208, 204, 123, 53, 65, 50, 249, 187, 233, 54, 135, 150, 80, 127, 128, 41, 235, 11, 35, 241, 28, 202, 197, 239, 196, 186, 198, 182, 31, 208, 2, 17, 0, 0, 0, 1, 6, 250, 242, 148, 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