Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e63c3fb5ffddc6cf57d0ad041a0a4dde5557ae814d0bad0c07fbbb90ae0ee5bc

Tx prefix hash: ec009e9d4469191b4e774689b818d9ee7bffa507958f5ec47dbde49639f7175b
Tx public key: 3c7ceb0ccbb84f957fb60c763f564a0de00941e06e2b767a94cd69ca5c673c22
Timestamp: 1705569423 Timestamp [UCT]: 2024-01-18 09:17:03 Age [y:d:h:m:s]: 01:039:20:49:29
Block: 937904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289553 RingCT/type: yes/0
Extra: 013c7ceb0ccbb84f957fb60c763f564a0de00941e06e2b767a94cd69ca5c673c220211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b9c8fffc87caf4bdaf1000cdb67b42f8e83522ae590e87ea211fdb58faa7267 0.600000000000 1395968 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": 937914, "vin": [ { "gen": { "height": 937904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b9c8fffc87caf4bdaf1000cdb67b42f8e83522ae590e87ea211fdb58faa7267" } } ], "extra": [ 1, 60, 124, 235, 12, 203, 184, 79, 149, 127, 182, 12, 118, 63, 86, 74, 13, 224, 9, 65, 224, 110, 43, 118, 122, 148, 205, 105, 202, 92, 103, 60, 34, 2, 17, 0, 0, 0, 3, 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