Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fabf6a43a50777b22d184eea19558305629e7b5346c5f85c15365821a050cbc

Tx prefix hash: aa4adb24c489657816bff4fc6a4799fec1479d6bead2a3357c6b95e483cb22bf
Tx public key: f1d07470b7688fae0c0834aaa8e78d70d74a1e9f0eec0531c7ee6091e6ad8744
Timestamp: 1760889309 Timestamp [UCT]: 2025-10-19 15:55:09 Age [y:d:h:m:s]: 00:065:10:27:49
Block: 1393451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46819 RingCT/type: yes/0
Extra: 01f1d07470b7688fae0c0834aaa8e78d70d74a1e9f0eec0531c7ee6091e6ad87440211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1de09ffe9e2ff6ce4f2b90d6825c4822b6d0553e6dafa572ad9d790ceb48dbf9 0.600000000000 1881716 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": 1393461, "vin": [ { "gen": { "height": 1393451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1de09ffe9e2ff6ce4f2b90d6825c4822b6d0553e6dafa572ad9d790ceb48dbf9" } } ], "extra": [ 1, 241, 208, 116, 112, 183, 104, 143, 174, 12, 8, 52, 170, 168, 231, 141, 112, 215, 74, 30, 159, 14, 236, 5, 49, 199, 238, 96, 145, 230, 173, 135, 68, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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