Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d937d0e669a877f6e846f3715eaac81d09759323a65a08936c0c7bf9950c0082

Tx prefix hash: a86a3930c7653788feb7b5187eec4a6ce3d5fb46759b43a2b8102b1b5d1b6f07
Tx public key: 1056c47490a80b750969421cbb90721be9052b203b56dd3306b2d7e08c04dbd6
Timestamp: 1752426171 Timestamp [UCT]: 2025-07-13 17:02:51 Age [y:d:h:m:s]: 00:163:00:54:53
Block: 1324735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115292 RingCT/type: yes/0
Extra: 011056c47490a80b750969421cbb90721be9052b203b56dd3306b2d7e08c04dbd60211000000072609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3551574ffd08c8ca4cf7ad499e7e9ce5c58633c3600d5272c2675ff22fd3fcb6 0.600000000000 1812478 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": 1324745, "vin": [ { "gen": { "height": 1324735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3551574ffd08c8ca4cf7ad499e7e9ce5c58633c3600d5272c2675ff22fd3fcb6" } } ], "extra": [ 1, 16, 86, 196, 116, 144, 168, 11, 117, 9, 105, 66, 28, 187, 144, 114, 27, 233, 5, 43, 32, 59, 86, 221, 51, 6, 178, 215, 224, 140, 4, 219, 214, 2, 17, 0, 0, 0, 7, 38, 9, 179, 160, 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