Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c380fe56edf0f5d4672f9a531fb09c7fbc609f74bddfcfcd5a543c5a565ca57

Tx prefix hash: 6f9ec020f8d8d538666063b8619a88ac9f2afbd96ea91298e6e39c5944aee757
Tx public key: 0c5353d1f38abfb0a5769349b317ffc4b19c8d90c1af12e233598b7133faed10
Timestamp: 1751821012 Timestamp [UCT]: 2025-07-06 16:56:52 Age [y:d:h:m:s]: 00:137:05:04:03
Block: 1320057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96461 RingCT/type: yes/0
Extra: 010c5353d1f38abfb0a5769349b317ffc4b19c8d90c1af12e233598b7133faed1002110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfa58e94689d91f815d2c73e08b9e4ab1f479f0972390a0317c2fa7190fd6d3b 0.600000000000 1807752 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": 1320067, "vin": [ { "gen": { "height": 1320057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfa58e94689d91f815d2c73e08b9e4ab1f479f0972390a0317c2fa7190fd6d3b" } } ], "extra": [ 1, 12, 83, 83, 209, 243, 138, 191, 176, 165, 118, 147, 73, 179, 23, 255, 196, 177, 156, 141, 144, 193, 175, 18, 226, 51, 89, 139, 113, 51, 250, 237, 16, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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