Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4afc0de940221497b4d3f0b5d94024bfa6a0402abf3a9a5f7d79aaf47e7be405

Tx prefix hash: ed8528de0e4d3d7a139e3e8ebead0b6ff31bfca021ce391605768b689c008f8b
Tx public key: 7a606343e94e42d3afebb24e7dabd4b42057096a6e323da1ab9762341eb80412
Timestamp: 1719540852 Timestamp [UCT]: 2024-06-28 02:14:12 Age [y:d:h:m:s]: 00:282:05:03:22
Block: 1053742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201651 RingCT/type: yes/0
Extra: 017a606343e94e42d3afebb24e7dabd4b42057096a6e323da1ab9762341eb8041202110000000250ac44b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6453739e561f47f0d2b310923e77dd22d8270e44e0bc32ae48ab3f7a5b86179f 0.600000000000 1524091 of 15

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": 1053752, "vin": [ { "gen": { "height": 1053742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6453739e561f47f0d2b310923e77dd22d8270e44e0bc32ae48ab3f7a5b86179f" } } ], "extra": [ 1, 122, 96, 99, 67, 233, 78, 66, 211, 175, 235, 178, 78, 125, 171, 212, 180, 32, 87, 9, 106, 110, 50, 61, 161, 171, 151, 98, 52, 30, 184, 4, 18, 2, 17, 0, 0, 0, 2, 80, 172, 68, 182, 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