Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3e45e183386d33f0f264313bb003e0c977152c5185c373665e0a2cbec3c774d

Tx prefix hash: 32d847a48339637aa7bd927065e46eea0464ebf12f348f3957ce22c1b661924a
Tx public key: af81e67d34da6e20a97f878ebe3255e3a9c3f37031e446088e1c8327dd6aa3a9
Timestamp: 1720424308 Timestamp [UCT]: 2024-07-08 07:38:28 Age [y:d:h:m:s]: 00:203:09:21:54
Block: 1061081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145287 RingCT/type: yes/0
Extra: 01af81e67d34da6e20a97f878ebe3255e3a9c3f37031e446088e1c8327dd6aa3a9021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f041ae9905d6296bf28f93e677d4891a479f7ea0f7dfd3a10f490d450d86936 0.600000000000 1531572 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": 1061091, "vin": [ { "gen": { "height": 1061081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f041ae9905d6296bf28f93e677d4891a479f7ea0f7dfd3a10f490d450d86936" } } ], "extra": [ 1, 175, 129, 230, 125, 52, 218, 110, 32, 169, 127, 135, 142, 190, 50, 85, 227, 169, 195, 243, 112, 49, 228, 70, 8, 142, 28, 131, 39, 221, 106, 163, 169, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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