Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a98e09ff0e565aef8d0298977c65567cf859750e7b90dbce73eb612625bda0f

Tx prefix hash: c28364b1b61be1b02c6e2056ccad27da9615514ce6e4eff6314d9b2ac343fb1a
Tx public key: e57330505e87615a547c83f1d4a2e7c2a5dec77b7e5e632c3ea4ba4102f84e09
Timestamp: 1576424435 Timestamp [UCT]: 2019-12-15 15:40:35 Age [y:d:h:m:s]: 05:149:22:25:47
Block: 27362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1253994 RingCT/type: yes/0
Extra: 01e57330505e87615a547c83f1d4a2e7c2a5dec77b7e5e632c3ea4ba4102f84e09021100000026ad433a0b000000000000000000

1 output(s) for total of 498.125989730000 dcy

stealth address amount amount idx
00: 7fe3e8aae9de163f7ab0a4794960e75c3054781a7a84a341f04e0ef1b7235e7e 498.125989730000 45358 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": 27372, "vin": [ { "gen": { "height": 27362 } } ], "vout": [ { "amount": 498125989730, "target": { "key": "7fe3e8aae9de163f7ab0a4794960e75c3054781a7a84a341f04e0ef1b7235e7e" } } ], "extra": [ 1, 229, 115, 48, 80, 94, 135, 97, 90, 84, 124, 131, 241, 212, 162, 231, 194, 165, 222, 199, 123, 126, 94, 99, 44, 62, 164, 186, 65, 2, 248, 78, 9, 2, 17, 0, 0, 0, 38, 173, 67, 58, 11, 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