Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f858852d47068fc59de368dc956f560889797d486fbbdaa1e51d8a78ac73bb29

Tx prefix hash: 6972be828dc5f578540764a5025f050ef8e92a13d260407438d31db7a451d01b
Tx public key: 6343d158d9359aa2856d9a062f6ae4b6edc17c70e1883f1f62ae8169f8c78a3d
Timestamp: 1725642954 Timestamp [UCT]: 2024-09-06 17:15:54 Age [y:d:h:m:s]: 00:125:12:16:17
Block: 1104337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89766 RingCT/type: yes/0
Extra: 016343d158d9359aa2856d9a062f6ae4b6edc17c70e1883f1f62ae8169f8c78a3d021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38f5f4a104c9786d17e6b416304c29a96d7f5b1c9c01ea088f006d28b4baa4f0 0.600000000000 1581442 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": 1104347, "vin": [ { "gen": { "height": 1104337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38f5f4a104c9786d17e6b416304c29a96d7f5b1c9c01ea088f006d28b4baa4f0" } } ], "extra": [ 1, 99, 67, 209, 88, 217, 53, 154, 162, 133, 109, 154, 6, 47, 106, 228, 182, 237, 193, 124, 112, 225, 136, 63, 31, 98, 174, 129, 105, 248, 199, 138, 61, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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