Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fb14053a37097ce786fb5316facc4ac73d20223cd1b16b68c5949467438f11e

Tx prefix hash: b681459f778796edd4a6ea0daeb1f2f98fa5f36284109f11cc0deeab6fea5611
Tx public key: 2c4faed829f55fea51e782dca02a2738ec3d37a5d4e0af54bff01a1b5fcc8da6
Timestamp: 1696409098 Timestamp [UCT]: 2023-10-04 08:44:58 Age [y:d:h:m:s]: 01:213:04:10:45
Block: 862171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413425 RingCT/type: yes/0
Extra: 012c4faed829f55fea51e782dca02a2738ec3d37a5d4e0af54bff01a1b5fcc8da6021100000004faf35c9c000000000000000000

1 output(s) for total of 0.853629886000 dcy

stealth address amount amount idx
00: cf081b8a3aa358c913ddc1844fa3e624393fb6cb75025616e8cd05c6d62d805e 0.853629886000 1316573 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": 862181, "vin": [ { "gen": { "height": 862171 } } ], "vout": [ { "amount": 853629886, "target": { "key": "cf081b8a3aa358c913ddc1844fa3e624393fb6cb75025616e8cd05c6d62d805e" } } ], "extra": [ 1, 44, 79, 174, 216, 41, 245, 95, 234, 81, 231, 130, 220, 160, 42, 39, 56, 236, 61, 55, 165, 212, 224, 175, 84, 191, 240, 26, 27, 95, 204, 141, 166, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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