Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43ec37a43c9d5b0ab2710596d20225e5a4a723fee43b973dad1f76a43acb5848

Tx prefix hash: 61681ed7bba03d41439697a65fd92826f8b934cd01f0c5a11132f127cdd8fe31
Tx public key: b25504df09c27a284b577cd21f622886c2ae2b6fbc3e4adedaabf8cddb9b1ac6
Timestamp: 1717853115 Timestamp [UCT]: 2024-06-08 13:25:15 Age [y:d:h:m:s]: 00:144:05:54:43
Block: 1039756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103251 RingCT/type: yes/0
Extra: 01b25504df09c27a284b577cd21f622886c2ae2b6fbc3e4adedaabf8cddb9b1ac602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c04928597ec8fb3ea52a76d96fee5a48b7935eeeabb9db745de85546f2a861b1 0.600000000000 1508411 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": 1039766, "vin": [ { "gen": { "height": 1039756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c04928597ec8fb3ea52a76d96fee5a48b7935eeeabb9db745de85546f2a861b1" } } ], "extra": [ 1, 178, 85, 4, 223, 9, 194, 122, 40, 75, 87, 124, 210, 31, 98, 40, 134, 194, 174, 43, 111, 188, 62, 74, 222, 218, 171, 248, 205, 219, 155, 26, 198, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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