Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 848571442cea001a9af72d30dfdd0fc7567f66b4ddf39664e314f50d411de2f8

Tx prefix hash: f0adc70220a82fbbf254d4cc715a716b2c29343c905cea9c373be505f2cdfbea
Tx public key: 02143b92136b0f464f83b214a089bead0e4e8679648578a8226a53743de5d1d7
Timestamp: 1730149359 Timestamp [UCT]: 2024-10-28 21:02:39 Age [y:d:h:m:s]: 00:155:12:19:52
Block: 1141629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110963 RingCT/type: yes/0
Extra: 0102143b92136b0f464f83b214a089bead0e4e8679648578a8226a53743de5d1d7021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00cf78bdedf586be3e00fe6eacfe1e4ce7ebf1befd9e4a10082063a312ae80f6 0.600000000000 1625438 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": 1141639, "vin": [ { "gen": { "height": 1141629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00cf78bdedf586be3e00fe6eacfe1e4ce7ebf1befd9e4a10082063a312ae80f6" } } ], "extra": [ 1, 2, 20, 59, 146, 19, 107, 15, 70, 79, 131, 178, 20, 160, 137, 190, 173, 14, 78, 134, 121, 100, 133, 120, 168, 34, 106, 83, 116, 61, 229, 209, 215, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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