Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e256fc8305c521e12afd57abe080cc07b647cedf473f1081ce26510c437e528

Tx prefix hash: cb930a1cab87158ea7c6c5a24b87f6dfdfaec987179281a1440e00e8f53f738e
Tx public key: 97746944f66f7b3b294febe76e26f6dfa187260706f8b7df3c87a9b857621e20
Timestamp: 1734156045 Timestamp [UCT]: 2024-12-14 06:00:45 Age [y:d:h:m:s]: 00:183:02:11:45
Block: 1174821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130592 RingCT/type: yes/0
Extra: 0197746944f66f7b3b294febe76e26f6dfa187260706f8b7df3c87a9b857621e200211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45a7a9e2a7abe517224232ece98ec60fdff1a9174724a8ea3ef58d2a15c85bf3 0.600000000000 1661020 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": 1174831, "vin": [ { "gen": { "height": 1174821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45a7a9e2a7abe517224232ece98ec60fdff1a9174724a8ea3ef58d2a15c85bf3" } } ], "extra": [ 1, 151, 116, 105, 68, 246, 111, 123, 59, 41, 79, 235, 231, 110, 38, 246, 223, 161, 135, 38, 7, 6, 248, 183, 223, 60, 135, 169, 184, 87, 98, 30, 32, 2, 17, 0, 0, 0, 6, 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