Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f71376a95bf8a2057a374b5be6b3500681887cf1274aa40842a9cd243ad006d

Tx prefix hash: 12dcc3e8ad24f2f96f5186c954321d2a25c7decc86b6b6063883b119e194a2f5
Tx public key: baccf337b5fb3fe74cb71f86ac5a950f982df3b8fd72e374fed5977022459532
Timestamp: 1698623805 Timestamp [UCT]: 2023-10-29 23:56:45 Age [y:d:h:m:s]: 01:116:17:11:43
Block: 880551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344368 RingCT/type: yes/0
Extra: 01baccf337b5fb3fe74cb71f86ac5a950f982df3b8fd72e374fed59770224595320211000000024b8f5122000000000000000000

1 output(s) for total of 0.741940391000 dcy

stealth address amount amount idx
00: 913dfb5320eabf38c7fb3627550d7a3d96a6ec932be3cd1cd8330045b1ea0ade 0.741940391000 1336109 of 0

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": 880561, "vin": [ { "gen": { "height": 880551 } } ], "vout": [ { "amount": 741940391, "target": { "key": "913dfb5320eabf38c7fb3627550d7a3d96a6ec932be3cd1cd8330045b1ea0ade" } } ], "extra": [ 1, 186, 204, 243, 55, 181, 251, 63, 231, 76, 183, 31, 134, 172, 90, 149, 15, 152, 45, 243, 184, 253, 114, 227, 116, 254, 213, 151, 112, 34, 69, 149, 50, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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