Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1ca3685bd16523a11bf63081e92a098d7443b579bb5f6f0b1f2b455a453815d

Tx prefix hash: 16d90fd1569d1d2063f6e4c6e4d3a3665ebb7e70ac8107e78c51233d964de427
Tx public key: 23260b22b4bf36616ffde929aa816fd1933e14feda96a2c230cd4508c1bd9df6
Timestamp: 1754351608 Timestamp [UCT]: 2025-08-04 23:53:28 Age [y:d:h:m:s]: 00:114:16:28:33
Block: 1340402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80972 RingCT/type: yes/0
Extra: 0123260b22b4bf36616ffde929aa816fd1933e14feda96a2c230cd4508c1bd9df60211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 501ebfd614691251f92c78ff2a8383a5e76a4813e31860bd563f8dedee4eb28b 0.600000000000 1828219 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": 1340412, "vin": [ { "gen": { "height": 1340402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "501ebfd614691251f92c78ff2a8383a5e76a4813e31860bd563f8dedee4eb28b" } } ], "extra": [ 1, 35, 38, 11, 34, 180, 191, 54, 97, 111, 253, 233, 41, 170, 129, 111, 209, 147, 62, 20, 254, 218, 150, 162, 194, 48, 205, 69, 8, 193, 189, 157, 246, 2, 17, 0, 0, 0, 3, 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