Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 586d2c1c1076ce37cdfbcac8b4a0b94076cb974d3deba26fedadec799b6648f1

Tx prefix hash: df55a4b16972d8a38a4a0adf0932fdc0008a9862aa75d4c001c76adcfc9e2d1c
Tx public key: 8657a24f1dfa2b495be4c9cd2079d73d743c273ad7dbf8fdbd3f8db77fdc5139
Timestamp: 1735425305 Timestamp [UCT]: 2024-12-28 22:35:05 Age [y:d:h:m:s]: 00:084:09:59:45
Block: 1185309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60121 RingCT/type: yes/0
Extra: 018657a24f1dfa2b495be4c9cd2079d73d743c273ad7dbf8fdbd3f8db77fdc51390211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7874d6cdf36439e6bb61f878c6059fcf04d506f835be1b364d29142a2afe9bd4 0.600000000000 1671776 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": 1185319, "vin": [ { "gen": { "height": 1185309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7874d6cdf36439e6bb61f878c6059fcf04d506f835be1b364d29142a2afe9bd4" } } ], "extra": [ 1, 134, 87, 162, 79, 29, 250, 43, 73, 91, 228, 201, 205, 32, 121, 215, 61, 116, 60, 39, 58, 215, 219, 248, 253, 189, 63, 141, 183, 127, 220, 81, 57, 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