Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be25ec6f1e0baafadb3ebe27bc35da85d2bd794065f7b966d222839f075f2d2c

Tx prefix hash: 5eb6c10f877747f6e7deddd72cf95809c48c2c49a5029021eb4888b6a50f03bc
Tx public key: af703130ad12ced9f9e75bda0e2880c918e27b596ff49a1098cdefc34c3c9a98
Timestamp: 1744559273 Timestamp [UCT]: 2025-04-13 15:47:53 Age [y:d:h:m:s]: 00:265:03:53:13
Block: 1260670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187299 RingCT/type: yes/0
Extra: 01af703130ad12ced9f9e75bda0e2880c918e27b596ff49a1098cdefc34c3c9a98021100000004dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f0dd384d50c005d3a5b8a2882110d87b92465aac36eaae46e84c1c9443e3e2c 0.600000000000 1747831 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": 1260680, "vin": [ { "gen": { "height": 1260670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f0dd384d50c005d3a5b8a2882110d87b92465aac36eaae46e84c1c9443e3e2c" } } ], "extra": [ 1, 175, 112, 49, 48, 173, 18, 206, 217, 249, 231, 91, 218, 14, 40, 128, 201, 24, 226, 123, 89, 111, 244, 154, 16, 152, 205, 239, 195, 76, 60, 154, 152, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 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