Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f79c5dcf0170c84a486a90261cc356f455f3e22e3baa5f3997711c17b22ba1f5

Tx prefix hash: 04b295070728936fb8ade14bd9e0793ab7f1401000cf4cdc919bf117f8ae3e03
Tx public key: cee086eb5881ac8bd8dc44ca7a08212f68def04b5b307fa063862a2a1f6befe8
Timestamp: 1708335484 Timestamp [UCT]: 2024-02-19 09:38:04 Age [y:d:h:m:s]: 01:306:13:55:40
Block: 960853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477911 RingCT/type: yes/0
Extra: 01cee086eb5881ac8bd8dc44ca7a08212f68def04b5b307fa063862a2a1f6befe802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8dad030df8707f5fc60f8fbf162999e49a20c5012d975d2ffa26a072059d751 0.600000000000 1420440 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": 960863, "vin": [ { "gen": { "height": 960853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8dad030df8707f5fc60f8fbf162999e49a20c5012d975d2ffa26a072059d751" } } ], "extra": [ 1, 206, 224, 134, 235, 88, 129, 172, 139, 216, 220, 68, 202, 122, 8, 33, 47, 104, 222, 240, 75, 91, 48, 127, 160, 99, 134, 42, 42, 31, 107, 239, 232, 2, 17, 0, 0, 0, 5, 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