Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d56167ddcb7767960800e0900bb4efda203e53c51cd27905eb53d92a2d2aeab

Tx prefix hash: 29010207d40ff9c81b10d6e155dfa003e4e1cfbee8c042fc4061f9ea6a5e2a40
Tx public key: 351fbc7beda4935e4ea95b4d9d41282e7a227de9e001e5b6464babfc8b830f87
Timestamp: 1711921153 Timestamp [UCT]: 2024-03-31 21:39:13 Age [y:d:h:m:s]: 01:010:01:10:40
Block: 990589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268131 RingCT/type: yes/0
Extra: 01351fbc7beda4935e4ea95b4d9d41282e7a227de9e001e5b6464babfc8b830f8702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac6d11461b5ed1b0c8f4f4d1c8945dd3da104bfb43134efe967346065673d077 0.600000000000 1450911 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": 990599, "vin": [ { "gen": { "height": 990589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac6d11461b5ed1b0c8f4f4d1c8945dd3da104bfb43134efe967346065673d077" } } ], "extra": [ 1, 53, 31, 188, 123, 237, 164, 147, 94, 78, 169, 91, 77, 157, 65, 40, 46, 122, 34, 125, 233, 224, 1, 229, 182, 70, 75, 171, 252, 139, 131, 15, 135, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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