Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25af489db6d2515e6ff04245bb9478157413f035c796dc0c06407f54cdce1667

Tx prefix hash: 8d55fd252dec0ce7ebad81aae37c25f70cbac378d0b5e15c92bcf015bf0c8e6d
Tx public key: af0a0ce495cd07a92183763238a1dc43ffb7dac229677dc2377fe4d5d44d46ae
Timestamp: 1729937869 Timestamp [UCT]: 2024-10-26 10:17:49 Age [y:d:h:m:s]: 00:234:12:41:05
Block: 1139917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167329 RingCT/type: yes/0
Extra: 01af0a0ce495cd07a92183763238a1dc43ffb7dac229677dc2377fe4d5d44d46ae0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a576977b1e6d60d03d616429acbb096225487c3c1bdb09b4d3bff6382154293b 0.600000000000 1623704 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": 1139927, "vin": [ { "gen": { "height": 1139917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a576977b1e6d60d03d616429acbb096225487c3c1bdb09b4d3bff6382154293b" } } ], "extra": [ 1, 175, 10, 12, 228, 149, 205, 7, 169, 33, 131, 118, 50, 56, 161, 220, 67, 255, 183, 218, 194, 41, 103, 125, 194, 55, 127, 228, 213, 212, 77, 70, 174, 2, 17, 0, 0, 0, 4, 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