Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f5dce575694de3efc4a66b087dee4e2f8d9a1b722881a56f66a1fab82f4d52e

Tx prefix hash: 4573b7fa830510fe4437f842a61082992d948072f4bfa64a8c3966f37c7e0709
Tx public key: 226085a7e1a09302160e07009ac00dd506f4d69e2fca5b3cc239080decee5612
Timestamp: 1723780107 Timestamp [UCT]: 2024-08-16 03:48:27 Age [y:d:h:m:s]: 01:165:12:29:31
Block: 1088895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376685 RingCT/type: yes/0
Extra: 01226085a7e1a09302160e07009ac00dd506f4d69e2fca5b3cc239080decee5612021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a45748a7924f044e78aeefe66e1f53b44975cbc7597414059bd39cc25382f09a 0.600000000000 1563514 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": 1088905, "vin": [ { "gen": { "height": 1088895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a45748a7924f044e78aeefe66e1f53b44975cbc7597414059bd39cc25382f09a" } } ], "extra": [ 1, 34, 96, 133, 167, 225, 160, 147, 2, 22, 14, 7, 0, 154, 192, 13, 213, 6, 244, 214, 158, 47, 202, 91, 60, 194, 57, 8, 13, 236, 238, 86, 18, 2, 17, 0, 0, 0, 2, 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