Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f1601e3abc322806719ae905f92d8936269efdc2c1d2fa5d9350a7d45a907d8

Tx prefix hash: e2ff4beed4fd945edf2ee06750c23b285e8f5c8e3fa4a23870966a5ba90c2e07
Tx public key: 0685c79e0e3510819bfbea128b74bbd16aa492cd1443aea4b9a79e682e6b080e
Timestamp: 1737902519 Timestamp [UCT]: 2025-01-26 14:41:59 Age [y:d:h:m:s]: 00:143:03:54:44
Block: 1205773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102054 RingCT/type: yes/0
Extra: 010685c79e0e3510819bfbea128b74bbd16aa492cd1443aea4b9a79e682e6b080e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25ffdc08ea6b4cd41d6019a0b17a963d8660f948a9b41ec4e8a429b0fd7754a5 0.600000000000 1692472 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": 1205783, "vin": [ { "gen": { "height": 1205773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25ffdc08ea6b4cd41d6019a0b17a963d8660f948a9b41ec4e8a429b0fd7754a5" } } ], "extra": [ 1, 6, 133, 199, 158, 14, 53, 16, 129, 155, 251, 234, 18, 139, 116, 187, 209, 106, 164, 146, 205, 20, 67, 174, 164, 185, 167, 158, 104, 46, 107, 8, 14, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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