Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 890e3498a9e2e7cf8ee5d302389fc893cce8cb51aa56df5f61dfa62986b05450

Tx prefix hash: 04d1dcd4e0c29ddc8d8b381ef99555b7c8f55574022406ead4ff8a288d69e611
Tx public key: 167db5a8f4bd6a1a45518e342e0192a28028fabe375b9a3d8c126ef87d2d3cda
Timestamp: 1706449735 Timestamp [UCT]: 2024-01-28 13:48:55 Age [y:d:h:m:s]: 01:027:08:42:46
Block: 945189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280613 RingCT/type: yes/0
Extra: 01167db5a8f4bd6a1a45518e342e0192a28028fabe375b9a3d8c126ef87d2d3cda02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14964dea7a53cf26178b9394803910fa325df411809e5338fd1df57687e47bc7 0.600000000000 1403499 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": 945199, "vin": [ { "gen": { "height": 945189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14964dea7a53cf26178b9394803910fa325df411809e5338fd1df57687e47bc7" } } ], "extra": [ 1, 22, 125, 181, 168, 244, 189, 106, 26, 69, 81, 142, 52, 46, 1, 146, 162, 128, 40, 250, 190, 55, 91, 154, 61, 140, 18, 110, 248, 125, 45, 60, 218, 2, 17, 0, 0, 0, 4, 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