Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 260378ddcffc6d16e3d8196a3bbb624ff41978f89ff41d8ade39a084c6a40549

Tx prefix hash: 2585b821b86cd14800ed1708feca28cc1a96b9a023d6c7e79a598b82c8f12b99
Tx public key: a0fdfc757ff9e5a13e06804198053e005c7bc2ffce4ffc45d9237f36c9580c5c
Timestamp: 1716674927 Timestamp [UCT]: 2024-05-25 22:08:47 Age [y:d:h:m:s]: 00:298:21:10:12
Block: 1030001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213618 RingCT/type: yes/0
Extra: 01a0fdfc757ff9e5a13e06804198053e005c7bc2ffce4ffc45d9237f36c9580c5c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a39b2dc3a2d24ab54478b2e01f32562ec1b1688467bfd2a37f13f66a56be64e 0.600000000000 1498240 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": 1030011, "vin": [ { "gen": { "height": 1030001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a39b2dc3a2d24ab54478b2e01f32562ec1b1688467bfd2a37f13f66a56be64e" } } ], "extra": [ 1, 160, 253, 252, 117, 127, 249, 229, 161, 62, 6, 128, 65, 152, 5, 62, 0, 92, 123, 194, 255, 206, 79, 252, 69, 217, 35, 127, 54, 201, 88, 12, 92, 2, 17, 0, 0, 0, 2, 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