Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4edd7977101de0c0dd5c08197258982566a7eea7ed027e9661c8adf638c4a2b0

Tx prefix hash: 71cdf11f4fd612954ae66455414c7d1896fb2cea92c540c64e88648e3e596f11
Tx public key: fca4ed58a43df4d739760041ed882622ed23a1f8d1408c7acebded93f037a5ba
Timestamp: 1747274697 Timestamp [UCT]: 2025-05-15 02:04:57 Age [y:d:h:m:s]: 00:195:12:46:14
Block: 1283143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137461 RingCT/type: yes/0
Extra: 01fca4ed58a43df4d739760041ed882622ed23a1f8d1408c7acebded93f037a5ba02110000000f1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1b5bf9ca7a5c2b0f12defdd58f276623d4ffad85003cf6cd05e6fc4df221d09 0.600000000000 1770560 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": 1283153, "vin": [ { "gen": { "height": 1283143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1b5bf9ca7a5c2b0f12defdd58f276623d4ffad85003cf6cd05e6fc4df221d09" } } ], "extra": [ 1, 252, 164, 237, 88, 164, 61, 244, 215, 57, 118, 0, 65, 237, 136, 38, 34, 237, 35, 161, 248, 209, 64, 140, 122, 206, 189, 237, 147, 240, 55, 165, 186, 2, 17, 0, 0, 0, 15, 31, 144, 81, 122, 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