Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 242c762a81c4df6187135683f36fcbb513c9bfe1bf984a55fdd4c09a52c696ac

Tx prefix hash: 459782876358cb5b0ace9714c19d688afc9479872ef3beaf6f79ac9c9f7d95c5
Tx public key: 78166335bbaf873c62e33b321f2ca8751eed6ae0c5b910626a25dc9b311f9901
Timestamp: 1730718396 Timestamp [UCT]: 2024-11-04 11:06:36 Age [y:d:h:m:s]: 00:135:08:54:22
Block: 1146315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96614 RingCT/type: yes/0
Extra: 0178166335bbaf873c62e33b321f2ca8751eed6ae0c5b910626a25dc9b311f99010211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bee54173d15b73f5a42828e6be976c9235d563f3f1f14b6d315ea8579b96465 0.600000000000 1630932 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": 1146325, "vin": [ { "gen": { "height": 1146315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bee54173d15b73f5a42828e6be976c9235d563f3f1f14b6d315ea8579b96465" } } ], "extra": [ 1, 120, 22, 99, 53, 187, 175, 135, 60, 98, 227, 59, 50, 31, 44, 168, 117, 30, 237, 106, 224, 197, 185, 16, 98, 106, 37, 220, 155, 49, 31, 153, 1, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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