Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a350bea9724a88b29d15ea0d12dd0b65ce21cff0f5db9ba35a45394ff157e5d

Tx prefix hash: 358e4e171efd5b6c55e4d2b2563963da636a0df5c0a14b5f0b0e1da047030acb
Tx public key: e6882d99676e53cd884a95e0b7dc704bac961918d71376e565af8885de003d8e
Timestamp: 1737355514 Timestamp [UCT]: 2025-01-20 06:45:14 Age [y:d:h:m:s]: 00:331:07:13:29
Block: 1201238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234373 RingCT/type: yes/0
Extra: 01e6882d99676e53cd884a95e0b7dc704bac961918d71376e565af8885de003d8e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b4ae568c0092c16170e964b4e36f44d30dfaf6a9d525ec93cb1bae5d7fa1e41 0.600000000000 1687887 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": 1201248, "vin": [ { "gen": { "height": 1201238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b4ae568c0092c16170e964b4e36f44d30dfaf6a9d525ec93cb1bae5d7fa1e41" } } ], "extra": [ 1, 230, 136, 45, 153, 103, 110, 83, 205, 136, 74, 149, 224, 183, 220, 112, 75, 172, 150, 25, 24, 215, 19, 118, 229, 101, 175, 136, 133, 222, 0, 61, 142, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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