Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 713a551ebc1445244e405a3cf5d679e159023fb558bb655e49a9af6e15a1d748

Tx prefix hash: 3a680cdd742ebc322b38fce34e79268378a5f738db7a336203a52244586dc86c
Tx public key: 68fd56bc99261f604c8187a020d622efb702b3a7b1e9b4d7e959e4211f2270b0
Timestamp: 1708250619 Timestamp [UCT]: 2024-02-18 10:03:39 Age [y:d:h:m:s]: 01:052:15:36:35
Block: 960148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298660 RingCT/type: yes/0
Extra: 0168fd56bc99261f604c8187a020d622efb702b3a7b1e9b4d7e959e4211f2270b00211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4afad640b194c35db9d3b453412cc2e6ef1e0c13ec438aa172122cb8cff25ea 0.600000000000 1419709 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": 960158, "vin": [ { "gen": { "height": 960148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4afad640b194c35db9d3b453412cc2e6ef1e0c13ec438aa172122cb8cff25ea" } } ], "extra": [ 1, 104, 253, 86, 188, 153, 38, 31, 96, 76, 129, 135, 160, 32, 214, 34, 239, 183, 2, 179, 167, 177, 233, 180, 215, 233, 89, 228, 33, 31, 34, 112, 176, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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