Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26293b1ed5c4c0828d17bf551583efff3b584bcc0358d899e29d229c7177ba7b

Tx prefix hash: b8602f7a32ba4ec1c1e6f07bf9e0c11065d119a5b1957ffc35a07e9c6bddbf1a
Tx public key: 6b73e026c237041f1df41f2006d4b9c4d2de073a84dd40384bfa9dc473e174c4
Timestamp: 1722097520 Timestamp [UCT]: 2024-07-27 16:25:20 Age [y:d:h:m:s]: 00:183:13:56:04
Block: 1074944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131109 RingCT/type: yes/0
Extra: 016b73e026c237041f1df41f2006d4b9c4d2de073a84dd40384bfa9dc473e174c4021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37148c349c05d9df04615933e595a06825ff931e6f0a6e2bdb03e9e1ad747f89 0.600000000000 1547463 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": 1074954, "vin": [ { "gen": { "height": 1074944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37148c349c05d9df04615933e595a06825ff931e6f0a6e2bdb03e9e1ad747f89" } } ], "extra": [ 1, 107, 115, 224, 38, 194, 55, 4, 31, 29, 244, 31, 32, 6, 212, 185, 196, 210, 222, 7, 58, 132, 221, 64, 56, 75, 250, 157, 196, 115, 225, 116, 196, 2, 17, 0, 0, 0, 3, 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