Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fab7f231dd57066e3b8908d9a2c103e67d8c7f96dbd627372d17f09f42595737

Tx prefix hash: 03141e48954ef41adc4de826287f7cabaafaacee045685d801a008bc7eaa1d6b
Tx public key: 3a3d18603548380b5fbde2b5907ba13b071e84b208e8af86ed281148d0c3b5bb
Timestamp: 1735217717 Timestamp [UCT]: 2024-12-26 12:55:17 Age [y:d:h:m:s]: 00:309:03:40:01
Block: 1183622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218430 RingCT/type: yes/0
Extra: 013a3d18603548380b5fbde2b5907ba13b071e84b208e8af86ed281148d0c3b5bb02110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aef53641a4e1107594b608fa24e2fd203849e1691ae44dd595269f733143edd1 0.600000000000 1670069 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": 1183632, "vin": [ { "gen": { "height": 1183622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aef53641a4e1107594b608fa24e2fd203849e1691ae44dd595269f733143edd1" } } ], "extra": [ 1, 58, 61, 24, 96, 53, 72, 56, 11, 95, 189, 226, 181, 144, 123, 161, 59, 7, 30, 132, 178, 8, 232, 175, 134, 237, 40, 17, 72, 208, 195, 181, 187, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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