Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b21b73852bd773397c2e0f0bafd4bdb3742d19208855b1a6fb60f3f1468e5991

Tx prefix hash: ed5b7ead829fa91a014e4af2c92bbb4affeb1eca096b12205197ccdd912c50e0
Tx public key: c909bd76d74759862ae905db127fb32d175dee49940f33f6855519bcf48f6d7f
Timestamp: 1716211793 Timestamp [UCT]: 2024-05-20 13:29:53 Age [y:d:h:m:s]: 00:353:00:09:04
Block: 1026154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252331 RingCT/type: yes/0
Extra: 01c909bd76d74759862ae905db127fb32d175dee49940f33f6855519bcf48f6d7f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 766aa41410d3c42930b3bb512a2147b66088dfad78106a1e2c7a880284318a89 0.600000000000 1493083 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": 1026164, "vin": [ { "gen": { "height": 1026154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "766aa41410d3c42930b3bb512a2147b66088dfad78106a1e2c7a880284318a89" } } ], "extra": [ 1, 201, 9, 189, 118, 215, 71, 89, 134, 42, 233, 5, 219, 18, 127, 179, 45, 23, 93, 238, 73, 148, 15, 51, 246, 133, 85, 25, 188, 244, 143, 109, 127, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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