Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf5bb4b4a7e1cd9bbe725ee131289ea8e11b2aaef4fa919c7c95afbedf18c18f

Tx prefix hash: cf06cb0fff33e536f6f021cd4cbf09c8c4fb2f6744c26fd6634ce0861ce1c5d1
Tx public key: 36b60e2edada6af5ae055a79e2488e488e0cfaf3380b388c3412eda91faa345f
Timestamp: 1715193715 Timestamp [UCT]: 2024-05-08 18:41:55 Age [y:d:h:m:s]: 00:207:12:55:43
Block: 1017724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148552 RingCT/type: yes/0
Extra: 0136b60e2edada6af5ae055a79e2488e488e0cfaf3380b388c3412eda91faa345f0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1f471fafaf05d68ea91f657a6a9a79bc8dc2997088e1a6741d4a27271d82fcf 0.600000000000 1481509 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": 1017734, "vin": [ { "gen": { "height": 1017724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1f471fafaf05d68ea91f657a6a9a79bc8dc2997088e1a6741d4a27271d82fcf" } } ], "extra": [ 1, 54, 182, 14, 46, 218, 218, 106, 245, 174, 5, 90, 121, 226, 72, 142, 72, 142, 12, 250, 243, 56, 11, 56, 140, 52, 18, 237, 169, 31, 170, 52, 95, 2, 17, 0, 0, 0, 7, 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