Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11206009304513617b855697a1e4a3aa8538d94da12def0cb17b92893b35a34b

Tx prefix hash: 10e853e33bd77b165bf0ad0cd9a88cc3ea7bd540459fb490efdef0e530c4860b
Tx public key: d2c34526c9109256ad4fd77e0de2712f9a15b4dc94792e8aac00af2eb250f6ab
Timestamp: 1711757582 Timestamp [UCT]: 2024-03-30 00:13:02 Age [y:d:h:m:s]: 01:025:20:57:46
Block: 989238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279453 RingCT/type: yes/0
Extra: 01d2c34526c9109256ad4fd77e0de2712f9a15b4dc94792e8aac00af2eb250f6ab0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fe4250d9ed1386ce87d0596afcb250575c61f638c1c2323970a5683d7f54c74 0.600000000000 1449533 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": 989248, "vin": [ { "gen": { "height": 989238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fe4250d9ed1386ce87d0596afcb250575c61f638c1c2323970a5683d7f54c74" } } ], "extra": [ 1, 210, 195, 69, 38, 201, 16, 146, 86, 173, 79, 215, 126, 13, 226, 113, 47, 154, 21, 180, 220, 148, 121, 46, 138, 172, 0, 175, 46, 178, 80, 246, 171, 2, 17, 0, 0, 0, 1, 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